I want to tranfer few objects from SQL server2000 to 2005.
I used tranfer object task and defined the connection but i am getting the error cannot apply value null to property login:value cannot be null.
How can i solve the problem/
from
Sufian
Search this forum. Plenty of people have had the same problem.
-Jamie
I used the Transfer Objects Task to copy one database to another.
The both db's are on the same instance.
I chose these options for the transfer
-SourceConnection :My_Instance
-SourceDatabase :My_DB
-DestinationConnection :My_Instance
-DestinationDatabase :CopyOfMy_DB
-DropObjectsFirst =True
-IncludeExtendedProperties =Fasle
-CopyData =True
-ExistingData =Replace
-CopySchema =True
-UseCollation =True
IncludeDependentObjects =False
CopyAllObjects =True
The others options are set on FASLE
When I execute the package, I got an error message, the logins are dropped. I cannot connect to the database engine, even with my admin account.
I have to restore themaster database !
So my question is : why this SSIS task drop all the logins in sql server in place of just copy one database?
What's the solution for this problem?
Thanks for your comments !
Matt
Nobody knows ? 
Matt
|||
Hi Matt,
When CopyAllObjects is set to True, the source database and all associated objects are copied -- including logins. When DropObjectsFirst is also to True, SSIS (actually, the underlying SMO layer) attempts to drop all objects (including the logins!) before the copy takes place. Since your source and destination databases are on the same server, this puts the server in a bad state.
While not exactly a bug, this behaviour is a bit dangerous, and there are plans to make the validation "smarter" in the next release to prevent this sort of thing from happening.
To make a copy of your database, you should set CopyAllObjects to False, and set the appropriate fields under ObjectsToCopy to True. (ie. CopyAllTables, CopyAllViews).
Hope that helps!
~Matt
I used the Transfer Objects Task to copy one database to another.
The both db's are on the same instance.
I chose these options for the transfer
-SourceConnection : My_Instance
-SourceDatabase : My_DB
-DestinationConnection : My_Instance
-DestinationDatabase : CopyOfMy_DB
-DropObjectsFirst = True
-IncludeExtendedProperties = Fasle
-CopyData = True
-ExistingData = Replace
-CopySchema = True
-UseCollation = True
IncludeDependentObjects =False
CopyAllObjects = True
The others options are set on FASLE
When I execute the package, I got an error message, the logins are dropped. I cannot connect to the database engine, even with my admin account.
I have to restore the master database !
So my question is : why this SSIS task drop all the logins in sql server in place of just copy one database?
What's the solution for this problem?
Thanks for your comments !
Matt
Nobody knows ?
Matt|||
Hi Matt,
When CopyAllObjects is set to True, the source database and all associated objects are copied -- including logins. When DropObjectsFirst is also to True, SSIS (actually, the underlying SMO layer) attempts to drop all objects (including the logins!) before the copy takes place. Since your source and destination databases are on the same server, this puts the server in a bad state.
While not exactly a bug, this behaviour is a bit dangerous, and there are plans to make the validation "smarter" in the next release to prevent this sort of thing from happening.
To make a copy of your database, you should set CopyAllObjects to False, and set the appropriate fields under ObjectsToCopy to True. (ie. CopyAllTables, CopyAllViews).
Hope that helps!
~Matt
