We have purchased a new Development SQL Server that is running SQL Server 2005. Our existing Development SQL Server is running SQL 2000.
How can I move the DTS packages from the SQL 2000 server to the new SQL 2005 server? I will be upgrading them to SSIS at some point, but don't have the time now.
thanks
Hi,
I have an existing sql server 2000 installation on one server. I now need to take one 2000 DB and restore it to a new sql server 2005 installation (on a different server).
What is the best way to do this. I can not upgrade the sql server 2000 installation to 2005. Basically i hoping all i need to do is backup the 2000 db and then restore it on the new sql 2005 server.
Is this possible...thanks for all help.
Hello,I have a database in 2005 that I'd like to copy and attach in 2000. Is thispossible? if so, how do I do it? I've tried doing a number of things fromjust trying to attach to the db file to trying to export and import viaaccess and I can't seem to get anything to work.Any help would be greatly appreciated.Thanks!Rick
View 1 Replies View RelatedRecently moved a couple of dbs from SQL 2000 -> SQL 2005 (different machine). Just restored the dbs on the new server from a full backup of the old one. Everything is fine but...
Some queries are returning out-of-order results (for records added since the migration). I tracked this down to the indexes. I completely rebuilt and reorganized the indexes (online) through the manager interface. This helped provide correct ordering for existing records, but new records added since the re index are still out-of-order.
Looking for a way to permanently fix the indexes so I don't have to constantly rebuild them.
Thanks.
How to import database in SQL server 2005 from the SQL server 2000 ??
Good day ,
Does anyone know how to moe / copy database users from sql server 2000 to sql server 2005. I ave been successful will everything except this in my migration. I can copy the database users themselves but not the users under the security section.
Please help
I need to move the SQL Server 2000 Desktop Engine (MSDE) database and all jobs to the SQL Server 2005 Enterprise Edition.
- May I detach and attach the DB in my case?
- Where is the procedure to move the jobs from MSDE to SQL Server
2005?
I just installed SQL 2005 on a new box. I want to move a database from a SQL 2000 server to the new server. Can I detach the database, copy it and attach it in the new server without having problems?
I'm concerned that if the datafile is in SQL2000 format, when I connect it to SQL2005 server, will it still be in old format or will it upgrade?....or is this something you don't worry about....and why?
Thanks,
Craig
Hi Friends
When i open the DTS packages in the Management Studio for editing the DTS packages
I get an error prompt asking me for Installing the Sql Server 2000 Designer Components. I already have the Sql Server 2000 Client tools installed in my machine. Should i still install the designer components...Wont there be a crash in the Client tools side???
cheers
Vic
http://vicdba.blogspot.com
Hello All,
I am working on a migration project of my database(lets name it DB1), from SQL 2000 to SQL 2005. I have some DTS packages in my SQL 2000 database which also needs to be migrated to SSIS. These DTS packages currently interacts with other database(lets name it DB2) which is also in SQL 2000 and which does the data transmission. The real issue is that the other database(DB2) also has some DTS packages which also communicates with DB1 (the db to be upgraded) and so when i migrate my DB1 to SQL 2005, i will have to change my DB2 packages also (although the change will be minor). Now considering that in future I might also migrate my DB2 to SQL 2005 I wanted to know what will be the right approach to follow. One is to modify the DTS packages of DB2 to accmodate the change in connection and the other is to migrate the DTS packages of DB2 also to SSIS.
Can anyone help me with this one.
Thanks in Advance
Mitesh
I have been tasked with upgrading around 150 SQL Server 2000 DTS packages to SSIS in SQL Server 2005 standard edition. I made a backup of the 2000 database upon which the DTS packages operate and restored it to the SQL 2005 server. So far, so good. I have the database in place. Now I need to get the DTS packages themselves into the SLQ 2005 server. I think I need to check my install and make sure that I have the SQL Server 2000 DTS services installed on the SQL 2005 server. I can do that.
However, I wonder what would be the most effective way to physically get the packages from the SQL 2000 server to the SQL 2005 server. Should I use structured storage files? If so, how do I go about opening them in SQL 2005 in order to save them to SQL server 2005?
I should mention that these packages make heavy use of ActiveX scripting so I am looking at rewriting them from scratch to be SSIS packages. I just need the packages on the SQL Server 2005 box so I can make sure I am creating exactly the same functionality in 2005 as existed in SQL server 2000. Each DTS 2000 individual package tends to be fairly simple and I think I can greatly improve the process by consolidating them.
Thanks in advance for any advice.
S. Wells
Hi,
I have many sql 2000 DTS packages that I support from my development workstation running v2000 sp4. Packages are altered on the development machine and then go through a normal release mechanisms to production via testing servers etc.
I have recently installed the client tools for SQL Server 2005 on my desktop to evaluate the product. The 2005 DB instance is running on a seperate server.
So, I have dev edition of sql 2000 and 2005 client tools (including BI Dev studio etc) on my workstation.
I have recently had to make changes to a 2000 DTS package and used my 2000 enterprise manager to do so. No Problem- saved and tested fine on my workstation.
But when I try and release it to another server, or open the package using enterprise manager from another machine that does not have sql 2005 installed - I get an error message 'Unspecified error'. This I've seen before when trying to open packages created in v2000 , using v7 or where the service packs are different between machines.
Digging around my workstation and comparing some of the DLLs I know to be required to distribute DTS packages (from RDIST.txt) it seems that some of the SQL 2000 dll files have been updated by my 2005 installation.
E.g
DTSFFILE.DLL on my machine is 2000.85.1054.0 whilst on any 'clean' 2000 machine is at version v2000.80.760.0
Surely it cant be right that SQL 2005 has newer versions of components for SQL 2000 than is available with the latest SP for the actual product! Especially considering that the installation of 2005 does not even allow you to edit 2000 DTS packages through the management studio without a 'special' download' of the feature pack,(whihc by the way does not work very well either)
So am I to conclude that you can not run side by side installations of SQL 2000 and 2005 on a single machine and expect 2000 to run as it did previously
We are converted our DTS 2000 packages to Sql Server 2005 SSIS. I am getting following error on my ActiveX script that got converted. I am new to SSIS and DTS. Never ever worked with ActiveX also. So any help would be appreciated. Following is the script followed by error I get:
'**********************************************************************
' Visual Basic ActiveX Script
'************************************************************************
Function Main()
Dim oPkg
SET oPkg = DTSGlobalVariables.Parent
SET stpBeginJob = oPkg.Steps("DTSStep_DTSActiveScriptTask_1")
SET stpFinishedJob = oPkg.Steps("DTSStep_DTSActiveScriptTask_3")
IF DTSGlobalVariables("Count").Value > 0 THEN
stpFinishedJob.DisableStep = True
stpBeginJob.ExecutionStatus = DTSStepExecStat_Waiting
ELSE
stpFinishedJob.DisableStep = False
stpFinishedJob.ExecutionStatus = DTSStepExecStat_Waiting
END IF
Main = DTSTaskExecResult_Success
End Function
Error I get Is:
[ActiveX Script Task] Error: Retrieving the file name for a component failed with error code 0x000A39BC.
Thank You
Below is a migration plan that I've compiled to migrate SQL 2000 DTS packages to SSIS 2005. Once these DTS packages have been migrated i will need to create a job and schedule them in SQL 2005.
I would appreciate and feedback or questions on this migration plan.
Migration DTS 2000 packages to SSIS 2005:
1. Will need to save the current production DTS package as structure storage file. We do not have a UDL file. We set the data connections within each DTS package.
2. Go to Sql 2005 - ManagementLegacyData Transformation Services - right-click and open previous saved structure storage file.
3. Modify the DTS data creditentials to reflect the SQL 2005 connection data. Modify any SQL 2000 MAPI settings to utilize SQL 2005 new database mail. Save the package on SQL 2005.
4. After the modified DTS package has been updated and saved on SQL 2005, save this file as a structure storage file.
5. go to BIDS. Create a new SSIS project. Right-click on SSIS packages and select Migrate DTS 2000 package. This will migrate over the DTS 2000 package with the updated SQL 2005 data creditentails.
6. click on the package properties - protectionlevel and change it to dontsavesensitive.
7. right-click and select package configurations..., select to store data creditentials in xml format.
8. right-click on execute DTS 2000 package task, select Edit... and click on Load DTS2000 package internally. This will embed this task into the new SSIS package. Test the package. Continue if successful.
9. Use SSIS deployment functionality to move the package over to SQL 2005 Integration Services. Right-click on package and select Run Package, if successful, create a job and schedule it to run on SQL 2005 Agent.
10. When creating the Job under SQL Agent, change the Owner: of the job to reflect the owner of the new SSIS package. Schedule the job.
I've just coming up to speed on SSIS 2005. Therefore, this is what i've been able to piece together up to this point and I'm looking for some industry advice/feedback on whether or not this is a good migration plan. I need to provide a migration plan to management by 2/18. Thanks
Hi Experts
I am trying to schedule a legacy DTS 2000 package in 64 bit Sql Server 2005.
I cannot use the DTSRun tool on the Command prompt of the Sql 2005. What about dtexec ?Can i run Sql Server 2000 DTS packages from the Command Prompt.
Is DTS 2000 the only way to do that?
Any Advise is greatly appreciated
Vic.
I am having problem moving packages/solutions for one folder to other.
Is there any specific way that we have to do this.
I copyed a solution and pasteditin a shared folder and when i open it iam geting connection errors and package correpted errors.
i amy sound funny but pls can any of you tell me the procedure.
thanks
I have 55 dts packages on my production server which are to be moved on to our new server. Can anyone help me out in this regard
thanks
vas
Hi, all. I have more than 100 DTS packages on one server which need to be migrated to another new server. What's the easiest way to do it? I can do it by opening each package then using save as to save into another server. But I have more than 100, so it is kind of tedious to do it.
Is there a way like export those packages then import them? Or script them then run it? If yes, Let me know how.
Thank you in advance.
Wuchun
In sql server 2000 if we need to move a package from one database to another we have to move the package.
But is it the same in Sql server 2005 integration services.
let me know
hi,
Is there any way to export a set of variables from each other package??
Issues comes when you have to built five packages which share the same variables. It's very tedious and hard to re-write them every time...
Thanks for your time,
I need to move total of 50 DTS packages from SQL 2000 to SQL 2005.Could someone give me the best way to do this ?
Do I need to just save the package onto the new server OR do I use the DTS package migration wizard.
What are the problems that can arise ?
I know my problem is not directly associated w/ SSIS, so please forgive the post here. I figured this would be the "most" appropriate place to post this challenge.
We're attempting to edit a 2000 DTS package in Design mode from within the 2005 SQL Management Studio. To do this we downloaded/installed the following packages from the MS download site:
Microsoft SQL Server 2000 DTS Designer Components
Microsoft SQL Server 2005 Backward Compatibility Components
We're able to open the package in design mode from the Management Studio (Server > Management > Legacy > Data Transformation Services > DTS Package Name). But, when the DTS designer is open, the backspace and arrow keys won't respond in the Management Studio. They begin responding when we close the DTS designer. There are no error messages when we close the DTS designer.
Does anyone know of a fix or a workaround? Any help would be greatly appreciated.
Thanks, Mike
Hi guys,
I have tried to use the sp_help_revlogin script to move logins from a sql 2000 server to a sql 2005 server. It works for users that have a password. But if the password is blank it will fail. Is there a work around for this since I can't change the users passwords?
I have also tried SSIS package but that too doesn't work because of the same reason.
Can anyone help...
We have a new database server for SQL Server 2005. To use our old VS 2005 websites, which were connected toanother database server with SQL Server 2000, what should I do? Just change the server name of the connection stringin the Source code and/or Web.config? My preliminary testing seemed to be not effective.TIA,Jeffrey
View 2 Replies View Relatedhow can we manage the db transfer when we are upgrading from 2000 to 2005? what is the right way to do that? where can we find something to read about it?
View 1 Replies View RelatedWe have a problem with our SQL 2000 server which we know is a product bug.
Is there anyway of importing, Copying the sql 2000 table back down to SQL 7 until the issue is resolved,
many thanks
Hello,
I'm in the process of moving a SQL Server 2000 to a new server. I have installed the new server added the latest sp. When I try to restore the system databases (Master, msdb) I get the following error
"the database xxxx.bak Cannot be restored because it was created by a different version of the server restore database is terminating abnormally"
I have looked at everything that I know of and both servers seem to be running the same versions of everything.
Can I just export the databases the the new server?
thanks in advance for any help you can give.
Jason
Hi,
We have an old machine which holds SQL server 2000 database. We need to migrate a whole database to a new machine which has SQL server 2005.
When we tried to move whole database using Import and Export Wizard, only tables can be selected to import/export. However we want to import/export the whole database, including tables, stored procedure, view, etc. Which tool should we use?
Thanks.
Hi,
We have an old machine which holds SQL server 2000 database. We need to migrate a whole database to a new machine which has SQL server 2005.
When we tried to move whole database using Import and Export Wizard, only tables can be selected to import/export. However we want to import/export the whole database, including tables, stored procedure, view, etc. Which tool should we use?
Thanks.
Hi!
I have created i webpage whos has a logged in system which is cretead in VS 2005 with the function ASP.NET configuration.
And know will i move all databas to i a MSSQL 2000 there i only can have one databas, And know i have ASP.NET logged in Databas and one site databas.
I just wondering if its possible to make i virtual connection with MSSQL 2000? If not somebody has some idés for me?
I hope you can understand me.
Is there a way to move the primary log file for a database to another drive without doing this with a restore database operation? I have added a second log log file but now I would like to delete the one that was created when the database was created.
View 1 Replies View RelatedI need to move our production database to a brand new machine on our LAN.Both machines are running SQL2K. I'd like to place the production databasein a directory on the destination machine with a slightly different pathname than the source SQL server.How can I shrink the transaction log to the minimum size before I try themove? What is the best way to move the database to the new machine? Wehave Veritus Backup Exec.Regards,Charles MacLean
View 1 Replies View RelatedI have a MSSQL2000 box with a large database containing circa 150 SP's.I want to move the DB to another SQL machine, but many of the SP's havereferences to the name of the current machine. Is there any way tobatch edit the procedures to refer to the new server, disassociatingthe old machine completely?Tia,Graham
View 1 Replies View Related