I am trying to run a transfer database task in IS. The tasks fails saying that a defined role already exists in current database. This occurs if I try a destination overwrite to an existing database and even if the database is not currently allocated with destination overwrite = false.
Has anyone experienced these problems. I am just learning IS and have never experienced this type of problem with the old DTS version.
I am attempting to utilize the 'Transfer Database Task' to copy a SQL 2000 database to 2005. I would like to set up the task as a job to run nightly and update the 2005 database from 2000.
I have the DestinationOverwrite set to true, the Action set to Copy, the Method is DatabaseOnline.
I receive the following message... ERROR: errorCode=-1073548784 description=Executing the query CREATE ROLE[RSExecRole] failed with the following error: "User, group, or role 'RSExecRole' already exists in the current database..."
If I set overwrite to true...why is this an issue? Suggestions? Comments?
Hi, can you not use this task in Microsoft SQL Server Integration Services Designer Version 9.00.3042.00? It keeps giving me an error when I try to copy a DB using this task. Says I cannot use this task in this edition of SSIS. Is there another way to copy a db so that I can schedule it to run or is there a SP I need to download for this to work? I'm using SQL Server Express as well.
I have created a SSIS package that does nothing more than loop through all DBs and copies the userDBs to another server. However, I keep getting an error after the task has created the database during its execution of "Create Role" statements. Here is the error:
Error: The Execute method on the task returned error code 0x80131500 (ERROR : errorCode=-1073548784 description=Executing the query "CREATE ROLE [aspnet_WebEvent_FullAccess] " failed with the following error: "User, group, or role 'aspnet_WebEvent_FullAccess' already exists in the current database.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. helpFile= helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}). The Execute method must succeed, and indicate the result using an "out" parameter.
Now it appears to me that the Transfer DB task keeps using master as the current database even after it has created the new DB? Why would it does this when at the source the database role is under the usersDB?
I am having a problem using the "Transfer Database Task" in SSIS. I want to copy (and overwrite) DestDB with SourceDB on one SQL Server, while SourceDB stays online.
So, I add the task to my control flow and go into the properties. Here's how I have the editor setup:
When I set these options and hit ok, I get validation errors. For every file in the source database, I get an error in the Transfer Database Task, 'Could not find the file "d:\SourceDB_XX" in the source database "SourceDB"'.
Does anyone have any ideas as to why I am getting this or of a way to fix it? Any reason why it puts 2 's in the file path?
Hi everyone Can any one help me I am using Tranfer databse object task when I am trying to run it its throwing exception can not send null value in login name????
Help anyone!! I fighting with the same error. I've tried all the suggestions on the web and more. Nothing seems to work. Has anyone found an answer from Microsoft?
Error: The Execute method on the task returned error code 0x80131500 (ERROR : errorCode=-1073548784 description=Executing the query "EXEC dbo.sp_grantdbaccess @loginame = N'sctcsssoadmin', @name_in_db = N'ssoadmin' " failed with the following error: "User, group, or role 'ssoadmin' already exists in the current database.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. helpFile= helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}). The Execute method must succeed, and indicate the result using an "out" parameter.
I'm trying to set the DestinationDatabaseFiles property programmatically through an expression. I keep getting the error:
SSIS package "Package1.dtsx" starting.
SSIS breakpoint 'Break when the container receives the OnPreExecute event' at executable 'Transfer Database Task' has been hit
Error: 0xC002929C at Transfer Database Task, Transfer Database Task: The transfer file information "","","" is missing the filename.
Error: 0xC002929D at Transfer Database Task, Transfer Database Task: The transfer file information "","","" is missing the folder part.
Error: 0xC0024107 at Transfer Database Task: There were errors during task validation.
Warning: 0x80019002 at Package1: The Execution method succeeded, but the number of errors raised (4) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "Package1.dtsx" finished: Failure.
I'm setting the property to a variable, copyDestFiles, which I've tried numerous ways to set, the latest being in a script.
When I view the variable at runtime it looks like this: "Prod2.mdf","D:\Program Files\Microsoft SQL Server\Data","";"Prod_log2.ldf" ,"D:\Program Files\Microsoft SQL Server\Data",""
How does one set this property using an expression?
I have created a package to copy 10 tables from a database to another one. I have created a datasource with SQL Authentication mode. And it couldn't run until I changed the datasource connection to Windows Authentication mode. How could it be like that, it's just the authentication mode?
Is there anyone have the right answer for this situation?
I set up a basic Transfer Database task (online, copy) to copy a DB. It works great except for the fact that it isn't transferring the PK's and FK's. It also looks like it did not transfer the views. Any idea why? Anything else the Transfer Database task doesn't actually transfer?
The Database Trasnfer Task has failed with the following error......failed with the following error: "Invalid object name 'dbo.exampleViewName.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
I set up a task to do a transfer of a SQL 2000 db to SQL 2005 in Integration Services (selected my servers, dbs, and chose DatabaseOnline method). In debug mode it processes for a little while and finally errors with:
[2] Progress: Starting database transfer.. Step 1 out of 2 complete
Error: The Execute method on the task returned error code 0x80131500 (An exception occurred while executing a Transact-SQL statement.). The Execute method must succeed, and indicate the result using an "out" parameter.
Can't get over this error, and net searches reveal other postings similiar, but no answers.
SSIS database transfer task (with overwrite) from SQL 2k source to SQL 2k5 destination fails with:
Error: The Execute method on the task returned error code 0x80131500 (ERROR : errorCode=-1073548784 description=Executing the query "CREATE ROLE [RFRSH_USER] " failed with the following error: "User, group, or role 'RFRSH_USER' already exists in the current database.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. helpFile= helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}). The Execute method must succeed, and indicate the result using an "out" parameter.
The error seems the same regardless if the destination DB exists or not!
I am using the "Transfer SQL Server Objects Task" to copy some tables from database A to database B including data.
The tables, primary key constraints, Foreign key, data and all transfers nicely except for "DEFAULT CONSTRAINTS" on the tables.
I have failed to find any option in the "Transfer SQL Server Objects Task" task to explicitly say "copy default constraints". So I guess logically it should happen automatically but it doesn't. I hope it is not a bug :-)
In short, does the €śTransfer SQL Server Objects Task€? support distributed transactions?
In trying to use a €śTransfer SQL Server Objects Task€? in a container using a transaction on the container. The task is set to support the transaction. It is setup to copy table data from several tables from a non-domain server (sql server 2000) to a domain-based server (sql server 2005). I get an error stating, €śThis task can not participate in a transaction€?.
I am wondering if it means exactly what it says €“ this task in SSIS can€™t participate at all. Or does it mean that it won€™t in this scenario for some reason. I attempted a simple copy of data from mssql 2005 to mssql 2005 (same server) and the task still failed). MSDTC appears to be running properly on my machine and such (I can do a simple distributed transaction across linked server to the 2000 server in Query Analyzer (QA)). Also, MSDTC appears to be working on both servers with distributed transaction query tests in QA.
Here€™s the error info€¦
SSIS package "Development BusinessContacts and Products Migration.dtsx" starting. Information: 0x4001100A at Copy BusinessContacts Data: Starting distributed transaction for this container. Error: 0xC002F319 at Copy BusinessContacts database table data 1, Transfer SQL Server Objects Task: This task can not participate in a transaction. Task failed: Copy BusinessContacts database table data 1 Information: 0x4001100C at Copy BusinessContacts database table data 1: Aborting the current distributed transaction. Information: 0x4001100C at Copy BusinessContacts Data: Aborting the current distributed transaction. SSIS package "Development BusinessContacts and Products Migration.dtsx" finished: Failure. The program '[4700] Development BusinessContacts and Products Migration.dtsx: DTS' has exited with code 0 (0x0).
Using "Integration Services Project" template in Business Intelligence Studio. Using platforms Visual Studio 2005 along with SQL Server 2005.
Getting the error while trying to execute package after loading it programmaticaly.
I've just one task "Transfer SQL Server Objects Task" on my Integration Services package. But when I try to execute it from VS 2005 project programmaticaly, it gives the above mentioned error.
The commands I use:
Package pkg = new Package();
pkg = a.LoadPackage(@"C:Documents and SettingsabcMy DocumentsVisual Studio 2005ProjectslSSISSSISPackage.dtsx", null, true);
DTSExecResult dResult = pkg.Execute();
The the error comes like: error: 0xc0012024 The task Transfer SQL Server Objects Task cannot run on this edition of Integration Services. It requires higher level edition.
I have just been using the Import Data wizard in SSMS and when going through the wizard I checked the "Optimize for many tables" checkbox.
The resultant package contains a task called "Transfer Task". I've never heard of this before. Its not listed in the toolbox and its not documented in BOL.
It does some rather strange things as well.
From what I can determine it uses an XML manifest file (stored in c:documents and settings<user>Local settings emp) to construct a SSIS package on the fly which is then executed by an Execute Package Task. Its SourceDB property is always "smo_Pubs". Its DestinationDB property is always "smo_Pubs_xfred" There's no UI for it
All very peculiar.
What is it?
Where has it come from?
Did it arrive with SP1 or have I just never noticed it before?
Why is it preferable to a package with lots of data-flows?
As we all know logins and jobs aren't replicated when using AllwaysOn. What i wanna know is if the "tranfer login taks" will be enough to cover the transfer of logins between servers.
i am trying to transfer objects from SQL Server 2000 DB to SQL 2005 DB.
i have copy schema to true and i am only copying tables. when i have tried first time it worked fine but in next time it start to give error. here is the error description.
[Transfer SQL Server Objects Task] Error: Execution failed with the following error: "ERROR : errorCode=-1071636471 description=An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". helpFile=dtsmsg.rll helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}".
I am trying to copy a subset of tables, stored procedures, and views from one database to another database on a named instance of SQL Server 2005. I am attempting to use the Transfer SQL Server Objects task in Integration Services.
I am able to create both Source and Destination connections, and specify the objects I want to transfer. When I run the package, the task turns yellow while it's processing, then green when it completes.
At this point, no objects have been transferred to my destination database. No tables, no procs, no views, nothing. No error has been generated. No information is written to an SSIS log file, other than the fact that objects are being transferred, and then the package is finished.
Does this have something to do with the fact that I'm using a named instance of SQL Server 2005?
I am using SSIS Transfer SQL Server Objects Task to copy all the objects of a database to another without the data. The properties that i have set for this task is as:
When I execute this task, it fails (with the errorCode=-1073548784) at a point where it tries to create a table which is inside a schema, because the script for creating the table is executed before creating the schema. So, if have a table [Person].[Employee], the script "Create Table [Person].[Employee]" gives an error
The specified schema name "Person" either does not exist or you do not have permission to use it. It cannot be a permission related issue as am using the sa account to connect to both the source and the destination. Hence, I conclude that the SSIS task here tries to copy the table first without creating the schema and so the excution fails.
Is this a bug in SSIS? or am missing anything? and what can be the workaround this?
When i'm trying to transfer SQL Server Objects from a SQL Server 2000 Database to another i got the following error: [Transfer SQL Server Objects Task] Error: Table "bank" does not exist at the source.
This just appens in some spcific situations:
- When i select the tables i want to transfer, using the option "CopyAllTables" it works fine;
- When i use specific instance as source. Using the Development machine as source it works fine, when i use the machine from Pre-Production (the one i whant to use) it doesn't .
Does anybody know if the DTS Transfer Object Task transfers tables with IDENTITY INSERT enabled? I'm copying objects, along with their data to another database, but I need to retain the values in my IDENTITY columns. I will do some manual checking but this is fairly tedious and error prone.
I've checked the Books Online but I couldn't find anything that answers my question.
A little background... I have a 25GB database (called DevDB) that my co-workers use for SQL development. The data in this database isn't important and all I really need are the SQL objects. So instead of doing a database backup, which includes the data as well, I was planning on just copying the database objects to another database called DevObjects (on the same server) and backing it up instead. This is SQL 2005 SP2.
I've created an IS package and have 3 items...
1. Check for existance and drop DevObjects database. This is to eliminate the need for dropping the objects first. Successful.
2. Create a new database DevObjects. Successful.
3. Transfer SQL Server Objects Task. Fails.
My transfer objects task is setup like this:
The connections are to the same server, source db: DevDB, destination db: DevObjects.
DropObjectsFirst: False
IncludeExtendedProperties: True
CopyData: False
CopySchema: True
UseCollation: True
IncludeDependendObjects: True
CopyAllObjects: True
CopyDatabaseUsers: True
CopyDatabaseRoles: True
CopySqlServerLogins: False
CopyObjectLevelPermissions: True
CopyIndexes: True
CopyTriggers: True
CopyFullTextIndexes: True
CopyPrimaryKeys: True
CopyForeignKeys: True
GenerateScriptsInUnicode: True
I get an error trying to create a login that's not even in the database I am trying to copy the objects from. Since this is the same server, the login is already there.
Is there a way to not copy the server logins (so that CopyAllObjects works)?
Anyway, I got past that error by changing CopyAllObjects to False and setting all the subgroups to True. Now, I get an error creating one of the FK's, it seems that the PK it references isn't created first.
Is there a way to force creating the PK's before the FK's?
If I set CopyForeignKeys to False, then it completes successfully, but I need the FK's to be transferred as well. Any ideas?
Does anyone have a better way to accomplish what I'm trying to do?
I am facing problem while using Transfer SQL Server Object Task in SSIS, it is not importing table & its attributes.
The details settings of Transfer SQL Server Object Task as follows: clicking edit - Objects(left pane) Right pane Connection Source Connection existing server name 1 Source Database ganny1 Destination Connection existing server name 1 Destination Database ganny2 Destination copy objects Objects to copy - copy all tables - true Table Objects CopyPrimaryKeys - True CopyForiegnKeys - True
After setting all this configurations, Executing task, I am not able to get table in my destination database. Please suggest me to solve the issue.
All Sp's and UDF's in one base database have to be compiled into five identical databases located in the same SQL Server in order to keep all those five db's stored procedures synchronized.
I made a simple SSIS package which content one "Transfer SQL Server Objects Task" component.
Hardcoded connection/Source db/Destination db and setup properties as
"Drop object first" = True
"Copy All Stored procedures" = True
"Copy All UDF" = True
Then I executed the Package right from Visual Studio environment and after the substantial thinking finally it show me a green light.
But when I verified the result no Sp's in the destination database were re-compiled/copied from the source database.
What is the security requirement for running this task? I have no problem running this taks as a system administrator but all my users who are in the db_dtsltduser cannot run the same task successfully. They are DBOs in both databases involded in the task. Thank you in advance for your help.
Hello all :) First, sorry for my english but I don't practice everday So, I'm a new user of Microsoft SQL 2005 and I'm testing some functionalities in SSIS.
I used the Transfer Objects Task to copy one database to another. The both db's are on the same instance.
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??????
I have written an SSIS package with a Transfer SQLServer Objects task which I want to use to copy database objects from a SQL Server 2000 database to SQL Server 2005.
When I run this task, I find the following error:
[Transfer SQL Server Objects Task] Error: Execution failed with the following error: "Version80 database compatibility level is not supported
Is there a way around this aside from changing the compatibility level of my SQL Server 2005 database?
I am trying to move some tables from one database to another(both 2005) using SSIS. The tables are not dbo tables. I am using sql authentication for the source and windows authentication for the destination SMO conection.
I get the following error:
Error: 0xC002F325 at Transfer Tables from Beta To test, Transfer SQL Server Objects Task: Execution failed with the following error: "ERROR : errorCode=-1071636471 description=An OLE DB error has occurred. Error code: 0x80040E37.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E37 Description: "Invalid object name 'demo.rz_Analysis'.".
I don't believe that the fix to the above issue has made its way into an SP yet. Can anyone confirm/refute this, and/or state when the fix will become publicly available &/or give a workaround?
I'm currently having some trouble with the "Transfer SQL Server Objects Task". All I wanna do is to copy a simple database from one server (SQL2000) to another one (SQL2005).
A small excerpt from my settings:
DropObjectsFirst: true ExistingData: Replace All table options are set to true . No matter what I do the package always appends the data from the source to the destination database.