I am getting the following error when executing a Copy SQL Server Objects Task. If it helps these objects are User Defined functions and also this had worked in the past it is only after changing the destination server to one that is offsite, has a different OS then the source and also runs as a DC. We are running SQL 2000 Server Standard with Spk 3a on both boxes.
Step 'DTSStep_DTSTransferObjectsTask_6' failed
Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 42S02)
Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetRightsAbbreviations'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetRights'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetTerritoryAbbreviations'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetTerritories'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetShow'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetTvEpisodes'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetTvSegments'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.GetTvSegmentsString'.
Step Error code: 800400D0
Step Error Help File:SQLDMO80.hlp
Step Error Help Context ID:1131Check object owner. This is the most common reason which is clearly seen from the error message you provided.sql
Showing posts with label objects. Show all posts
Showing posts with label objects. Show all posts
Sunday, March 25, 2012
Wednesday, March 21, 2012
DTS copy all objects failed with invalid column name
I am trying to use the Import Data wizard to copy one database into
another on the same server and keep getting this error.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
'ColumnName'
There are 6 columns in the list and all of them either don't exist
anymore or have been moved to another table in the database. I don't
understand why it keeps trying to copy columns that either aren't
there or have been moved. It looks like the database has become
corrupted. Does anyone know how I might fix this?
Regards,
Aaron
I have also tried dropping all the tables, recreating them and
re-inserting the data and I still get these errors when trying to copy
the database.
|||I have also tried dropping all the tables, recreating them and
re-inserting the data and I still get these errors when trying to copy
the database.
Regards,
Aaron
another on the same server and keep getting this error.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
'ColumnName'
There are 6 columns in the list and all of them either don't exist
anymore or have been moved to another table in the database. I don't
understand why it keeps trying to copy columns that either aren't
there or have been moved. It looks like the database has become
corrupted. Does anyone know how I might fix this?
Regards,
Aaron
I have also tried dropping all the tables, recreating them and
re-inserting the data and I still get these errors when trying to copy
the database.
|||I have also tried dropping all the tables, recreating them and
re-inserting the data and I still get these errors when trying to copy
the database.
Regards,
Aaron
DTS copy all objects failed with invalid column name
I am trying to use the Import Data wizard to copy one database into
another on the same server and keep getting this error.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
'ColumnName'
There are 6 columns in the list and all of them either don't exist
anymore or have been moved to another table in the database. I don't
understand why it keeps trying to copy columns that either aren't
there or have been moved. It looks like the database has become
corrupted. Does anyone know how I might fix this?
Regards,
AaronI have also tried dropping all the tables, recreating them and
re-inserting the data and I still get these errors when trying to copy
the database.|||I have also tried dropping all the tables, recreating them and
re-inserting the data and I still get these errors when trying to copy
the database.
Regards,
Aaron
another on the same server and keep getting this error.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
'ColumnName'
There are 6 columns in the list and all of them either don't exist
anymore or have been moved to another table in the database. I don't
understand why it keeps trying to copy columns that either aren't
there or have been moved. It looks like the database has become
corrupted. Does anyone know how I might fix this?
Regards,
AaronI have also tried dropping all the tables, recreating them and
re-inserting the data and I still get these errors when trying to copy
the database.|||I have also tried dropping all the tables, recreating them and
re-inserting the data and I still get these errors when trying to copy
the database.
Regards,
Aaron
DTS causes TMPDB to expand on host Server
The Copy SQL Server Objects Task doesn't have this
functionality, as far as I know, so unless you've
programmed it yourself (select * into xxx from
server.database.owner.view) I don't see how this is
possible. By default, only the TSQL code to create the
views will be transferred.
Is this DTS work being done so you can do a nosync
initialization? If so, and you are taking the whole
database, you might want to look at backing up and
restoring the database, which would be much quicker.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Explain what you mean by a NOSYNC initialization, I am still learning. I had
thought about the backup and then restore, but was unsure if it would be
faster. I see by your reply, and by the time it has taken me, that indeed it
would be much faster.
I sincerely appreciate your help. I have not physically looked at the
production server, or how it had been set up, thus the comment about server
space.
Thank you again,
LS
"Paul Ibison" wrote:
> The Copy SQL Server Objects Task doesn't have this
> functionality, as far as I know, so unless you've
> programmed it yourself (select * into xxx from
> server.database.owner.view) I don't see how this is
> possible. By default, only the TSQL code to create the
> views will be transferred.
> Is this DTS work being done so you can do a nosync
> initialization? If so, and you are taking the whole
> database, you might want to look at backing up and
> restoring the database, which would be much quicker.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||It might be useful what is the requirement for
your 'clone'. The reason I ask is that replication might
not be the correct solution for your needs. On
www.ReplicationAnswers.Com in the articles section I have
put an article which details the differences between
replication and log shipping for the purposes of
maintaining a standby server. My suspicion is that log
shipping may be more relevant for you. If not, then I'll
help you set up replication once you've posted back.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I am setting up a test SQL server for our programmers to use, as opposed to
the production server. They do not need all of the databases on the
production server on the test server, but there does need to be some type of
replication of the databases used. I hope this explains what I am attempting
to do?
Many Thanks,
Larry S
"Paul Ibison" wrote:
> It might be useful what is the requirement for
> your 'clone'. The reason I ask is that replication might
> not be the correct solution for your needs. On
> www.ReplicationAnswers.Com in the articles section I have
> put an article which details the differences between
> replication and log shipping for the purposes of
> maintaining a standby server. My suspicion is that log
> shipping may be more relevant for you. If not, then I'll
> help you set up replication once you've posted back.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||LS,
will they be editing the data, or just doing selects?
What latency can you accept between the production server
and the backup (developer) box? This will help narrow
down the options.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
A little of both, the idea is to have a enviroment that the programmers can
do whatever they want, and if the development database is so corrupt, that it
can be replaced the next day from the production server. That is what would
be ideal. And what my supervisor would like to have in place.
I sincerely appreciate all your help,
Regards,
Larry S
"Paul Ibison" wrote:
> LS,
> will they be editing the data, or just doing selects?
> What latency can you accept between the production server
> and the backup (developer) box? This will help narrow
> down the options.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||In that case I'd use a different strategy. I'd copy over
the production database backup to the developer's server
and restore it, on a nightly schedule. If you used log
shipping, the database would have to be treated as read
only, and essentially the same for transactional
replication, where developer's changes could 'break' it.
So, I'd ship the database. If it is large, you might want
to zip it up befiore transferring across the network,
otherwise a job to transfer and a job on the standby
server to restore should be enough. If you only want a
subset of the database however, then you might want to
take a look at snapshot replication.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Please clarify: "subset" of the databases? I hate to sound ignorant, but what
you are saying essentially is to do a backup and restore daily of the used
databases,correct?
I appreciate your time and patience with me.
Regards,
LS
"Paul Ibison" wrote:
> In that case I'd use a different strategy. I'd copy over
> the production database backup to the developer's server
> and restore it, on a nightly schedule. If you used log
> shipping, the database would have to be treated as read
> only, and essentially the same for transactional
> replication, where developer's changes could 'break' it.
> So, I'd ship the database. If it is large, you might want
> to zip it up befiore transferring across the network,
> otherwise a job to transfer and a job on the standby
> server to restore should be enough. If you only want a
> subset of the database however, then you might want to
> take a look at snapshot replication.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Yes - backup and restore would seem to fit your needs.
However the developers might only need to work against eg
10 tables and there are 100 other ones in the production
database. In that case, snapshot replication would
probably be more useful, assuming you can cope with the
necessary table locks when the snapshot is generated.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
I think you are on target, as far as having to use table locks to backup
just the tables used should not be a problem. There will probably not be
enough of an area of concern to limit the back up / restore functionality.
I sincerely appreciate your help.
Regards,
Larry S
"Paul Ibison" wrote:
> Yes - backup and restore would seem to fit your needs.
> However the developers might only need to work against eg
> 10 tables and there are 100 other ones in the production
> database. In that case, snapshot replication would
> probably be more useful, assuming you can cope with the
> necessary table locks when the snapshot is generated.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
functionality, as far as I know, so unless you've
programmed it yourself (select * into xxx from
server.database.owner.view) I don't see how this is
possible. By default, only the TSQL code to create the
views will be transferred.
Is this DTS work being done so you can do a nosync
initialization? If so, and you are taking the whole
database, you might want to look at backing up and
restoring the database, which would be much quicker.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Explain what you mean by a NOSYNC initialization, I am still learning. I had
thought about the backup and then restore, but was unsure if it would be
faster. I see by your reply, and by the time it has taken me, that indeed it
would be much faster.
I sincerely appreciate your help. I have not physically looked at the
production server, or how it had been set up, thus the comment about server
space.
Thank you again,
LS
"Paul Ibison" wrote:
> The Copy SQL Server Objects Task doesn't have this
> functionality, as far as I know, so unless you've
> programmed it yourself (select * into xxx from
> server.database.owner.view) I don't see how this is
> possible. By default, only the TSQL code to create the
> views will be transferred.
> Is this DTS work being done so you can do a nosync
> initialization? If so, and you are taking the whole
> database, you might want to look at backing up and
> restoring the database, which would be much quicker.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||It might be useful what is the requirement for
your 'clone'. The reason I ask is that replication might
not be the correct solution for your needs. On
www.ReplicationAnswers.Com in the articles section I have
put an article which details the differences between
replication and log shipping for the purposes of
maintaining a standby server. My suspicion is that log
shipping may be more relevant for you. If not, then I'll
help you set up replication once you've posted back.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I am setting up a test SQL server for our programmers to use, as opposed to
the production server. They do not need all of the databases on the
production server on the test server, but there does need to be some type of
replication of the databases used. I hope this explains what I am attempting
to do?
Many Thanks,
Larry S
"Paul Ibison" wrote:
> It might be useful what is the requirement for
> your 'clone'. The reason I ask is that replication might
> not be the correct solution for your needs. On
> www.ReplicationAnswers.Com in the articles section I have
> put an article which details the differences between
> replication and log shipping for the purposes of
> maintaining a standby server. My suspicion is that log
> shipping may be more relevant for you. If not, then I'll
> help you set up replication once you've posted back.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||LS,
will they be editing the data, or just doing selects?
What latency can you accept between the production server
and the backup (developer) box? This will help narrow
down the options.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
A little of both, the idea is to have a enviroment that the programmers can
do whatever they want, and if the development database is so corrupt, that it
can be replaced the next day from the production server. That is what would
be ideal. And what my supervisor would like to have in place.
I sincerely appreciate all your help,
Regards,
Larry S
"Paul Ibison" wrote:
> LS,
> will they be editing the data, or just doing selects?
> What latency can you accept between the production server
> and the backup (developer) box? This will help narrow
> down the options.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||In that case I'd use a different strategy. I'd copy over
the production database backup to the developer's server
and restore it, on a nightly schedule. If you used log
shipping, the database would have to be treated as read
only, and essentially the same for transactional
replication, where developer's changes could 'break' it.
So, I'd ship the database. If it is large, you might want
to zip it up befiore transferring across the network,
otherwise a job to transfer and a job on the standby
server to restore should be enough. If you only want a
subset of the database however, then you might want to
take a look at snapshot replication.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Please clarify: "subset" of the databases? I hate to sound ignorant, but what
you are saying essentially is to do a backup and restore daily of the used
databases,correct?
I appreciate your time and patience with me.
Regards,
LS
"Paul Ibison" wrote:
> In that case I'd use a different strategy. I'd copy over
> the production database backup to the developer's server
> and restore it, on a nightly schedule. If you used log
> shipping, the database would have to be treated as read
> only, and essentially the same for transactional
> replication, where developer's changes could 'break' it.
> So, I'd ship the database. If it is large, you might want
> to zip it up befiore transferring across the network,
> otherwise a job to transfer and a job on the standby
> server to restore should be enough. If you only want a
> subset of the database however, then you might want to
> take a look at snapshot replication.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Yes - backup and restore would seem to fit your needs.
However the developers might only need to work against eg
10 tables and there are 100 other ones in the production
database. In that case, snapshot replication would
probably be more useful, assuming you can cope with the
necessary table locks when the snapshot is generated.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
I think you are on target, as far as having to use table locks to backup
just the tables used should not be a problem. There will probably not be
enough of an area of concern to limit the back up / restore functionality.
I sincerely appreciate your help.
Regards,
Larry S
"Paul Ibison" wrote:
> Yes - backup and restore would seem to fit your needs.
> However the developers might only need to work against eg
> 10 tables and there are 100 other ones in the production
> database. In that case, snapshot replication would
> probably be more useful, assuming you can cope with the
> necessary table locks when the snapshot is generated.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
Sunday, February 26, 2012
DTS - Copy Sql Server Objects help
Im trying to create a DTS Package to copy my sql Server objects to a test Server. The server Im copying from is UMTS1 and the server Im copying to is UMTSDEV.
The database name is ProgramSpecs and exists on bother servers. My login is assigned to all server roles on both servers. I have created databases on both servers manually so Im pretty sure I have all the necessary permissions. Im using the DTS task Copy Sql Server Objects to copy sql server objects and have selected Drop Destination objects first.
When I try to execute the package I get the following error:
Error source: MS SQL DMO
Error Description: Invalid OLEVERB Structure [SQL DMO] create file error or UMTS1.ProgramSpecs.LOG
Can anyone tell me what Im doing wrong?
Thanks
GEMDTS writes the necessary script files at C:\Program Files\Microsoft SQL Server\80\Tools (for sql2k provided u havent changed installation folders). check the content of the file UMTS1.ProgramSpecs.LOG at that folder. u may get the clue.|||I looked in C:\Program Files\Microsoft SQL Server\80\Tools and was unable to find the file you mentioned. I looked in the directory on my local drive and on the server and was unable to find the file. The installation folders for SQL Server haven't been changed from the default during the installation.|||Are the specs exactly the same on both servers? Including collation?
You can find this out by right-clicking on the database in Enterprise Manager and select Properties. They should match.|||I looked in C:\Program Files\Microsoft SQL Server\80\Tools and was unable to find the file you mentioned. I looked in the directory on my local drive and on the server and was unable to find the file. The installation folders for SQL Server haven't been changed from the default during the installation.
ok, if not in the folder i mentioned, check the "Script file directory" textbox in the "copy" tab of the DTS step. you must find the file there. at times missing dependent objects causes the copy to fail.
alternatively u can use backup/restore to make a copy of a database. its easy.|||I was going to say - why are we DTS'ing this when we could backup and restore to the test environment?
That's what we do over here and it's never caused us any problems :)|||I want to use the DTS package so I can select which objects to copy. I have already converted my initial data from an MS Access database which was a real chore. I m now in the process of creating a website and stored procedures. I think if I just do a restore database, I would loose all of the stored procedures Im in the process of creating. So unless I duplicated any new store procedures I developed in the other database I would loose them when I restored. If I copied the objects using DTS I could only copy the tables and data.
Another option I have considered is to create a second database that only had views and stored procedures that referenced the original database.
Example for northwind:
Northwind (original Database)
Northwind_Web (Web Database)
Nortwind has a table called tblEmployees(I think). The database Northwind_web would have a VIEW called tblEmployees and the select statement would be Select * from Northwind.dbo.tblEmployees. All of my updates, deletions and appends would be done through the views. Then when I got ready to go live all I would have to do is script the procs from Northwind_web to Northwind and it should work because instead of updating views, the tables would automatically be updated because the names are the same.
Another option I have thought about is to simply use Update Northwind.dbo.TblEmployees instead of just update tblEmployees in my procs . Either way I would have a separate database; one for just the data and one for the views and stored procedures that updated the original database. Then I could just restore the Northwind database when I wanted to refresh the data.
My questions are: How stupid is this? What would the affect on performance be having 2 databases? If I decide to go with a restore only, can you restore only data without the stored procedures and views?
The database name is ProgramSpecs and exists on bother servers. My login is assigned to all server roles on both servers. I have created databases on both servers manually so Im pretty sure I have all the necessary permissions. Im using the DTS task Copy Sql Server Objects to copy sql server objects and have selected Drop Destination objects first.
When I try to execute the package I get the following error:
Error source: MS SQL DMO
Error Description: Invalid OLEVERB Structure [SQL DMO] create file error or UMTS1.ProgramSpecs.LOG
Can anyone tell me what Im doing wrong?
Thanks
GEMDTS writes the necessary script files at C:\Program Files\Microsoft SQL Server\80\Tools (for sql2k provided u havent changed installation folders). check the content of the file UMTS1.ProgramSpecs.LOG at that folder. u may get the clue.|||I looked in C:\Program Files\Microsoft SQL Server\80\Tools and was unable to find the file you mentioned. I looked in the directory on my local drive and on the server and was unable to find the file. The installation folders for SQL Server haven't been changed from the default during the installation.|||Are the specs exactly the same on both servers? Including collation?
You can find this out by right-clicking on the database in Enterprise Manager and select Properties. They should match.|||I looked in C:\Program Files\Microsoft SQL Server\80\Tools and was unable to find the file you mentioned. I looked in the directory on my local drive and on the server and was unable to find the file. The installation folders for SQL Server haven't been changed from the default during the installation.
ok, if not in the folder i mentioned, check the "Script file directory" textbox in the "copy" tab of the DTS step. you must find the file there. at times missing dependent objects causes the copy to fail.
alternatively u can use backup/restore to make a copy of a database. its easy.|||I was going to say - why are we DTS'ing this when we could backup and restore to the test environment?
That's what we do over here and it's never caused us any problems :)|||I want to use the DTS package so I can select which objects to copy. I have already converted my initial data from an MS Access database which was a real chore. I m now in the process of creating a website and stored procedures. I think if I just do a restore database, I would loose all of the stored procedures Im in the process of creating. So unless I duplicated any new store procedures I developed in the other database I would loose them when I restored. If I copied the objects using DTS I could only copy the tables and data.
Another option I have considered is to create a second database that only had views and stored procedures that referenced the original database.
Example for northwind:
Northwind (original Database)
Northwind_Web (Web Database)
Nortwind has a table called tblEmployees(I think). The database Northwind_web would have a VIEW called tblEmployees and the select statement would be Select * from Northwind.dbo.tblEmployees. All of my updates, deletions and appends would be done through the views. Then when I got ready to go live all I would have to do is script the procs from Northwind_web to Northwind and it should work because instead of updating views, the tables would automatically be updated because the names are the same.
Another option I have thought about is to simply use Update Northwind.dbo.TblEmployees instead of just update tblEmployees in my procs . Either way I would have a separate database; one for just the data and one for the views and stored procedures that updated the original database. Then I could just restore the Northwind database when I wanted to refresh the data.
My questions are: How stupid is this? What would the affect on performance be having 2 databases? If I decide to go with a restore only, can you restore only data without the stored procedures and views?
Tuesday, February 14, 2012
DSV Refresh
Hi,
I have an odd problem with the creation of objects in the data source view using AMO.
I added some tables and relations with AMO and everything seems to work well.
Then, using Analysis Services I selected the data source view and refreshed it.
The form that notifies the changes in the data source view showed a lot of changes that I didn’t understand, costraints created and removed, fields changed and other operations that I didn’t made...
I try to do the refresh with AMO using all the update and refresh options I found but with no results.
Every insight on the question will be of great help.
Thanks
This is an extract of the data source view refresh report:
Object
Change
_DIM_DimColl1
Changed
Constraint1
Deleted
_DIM_Dimensione
attrfinto
Changed
_DIM_eta2
aaa
Changed
_DIM_Mesi
Changed
_DIM_MesiColl
Changed
Constraint1
Deleted
_FK_eta2_aaa
Changed
Constraint1
Deleted
_FK_MesiColl_Livello03
Changed
Constraint1
I don't have a clue what's causing that, but let me suggest that you keep a copy of the .dsv (XML) file from before you refresh the DSV. Then you refresh it, save it, and do a diff versus the previous file. Then you can see exactly what properties changed. There's a pretty close mapping between AMO properties and the XML elements in the file.|||The refresh in AMO is different from the refresh in DSV diagram. DSV Diagram refresh will connect to the relational database and refresh the metadata. AMO refresh will not connect to relational database and just refresh the objects within AMO.|||
Do you know how can I refresh the DSV through AMO?
DSV Refresh
Hi,
I have an odd problem with the creation of objects in the data source view using AMO.
I added some tables and relations with AMO and everything seems to work well.
Then, using Analysis Services I selected the data source view and refreshed it.
The form that notifies the changes in the data source view showed a lot of changes that I didn’t understand, costraints created and removed, fields changed and other operations that I didn’t made...
I try to do the refresh with AMO using all the update and refresh options I found but with no results.
Every insight on the question will be of great help.
Thanks
This is an extract of the data source view refresh report:
Object
Change
_DIM_DimColl1
Changed
Constraint1
Deleted
_DIM_Dimensione
attrfinto
Changed
_DIM_eta2
aaa
Changed
_DIM_Mesi
Changed
_DIM_MesiColl
Changed
Constraint1
Deleted
_FK_eta2_aaa
Changed
Constraint1
Deleted
_FK_MesiColl_Livello03
Changed
Constraint1
I don't have a clue what's causing that, but let me suggest that you keep a copy of the .dsv (XML) file from before you refresh the DSV. Then you refresh it, save it, and do a diff versus the previous file. Then you can see exactly what properties changed. There's a pretty close mapping between AMO properties and the XML elements in the file.|||The refresh in AMO is different from the refresh in DSV diagram. DSV Diagram refresh will connect to the relational database and refresh the metadata. AMO refresh will not connect to relational database and just refresh the objects within AMO.|||
Do you know how can I refresh the DSV through AMO?
Subscribe to:
Posts (Atom)