DTS Pkgs
Jan 23, 2008Is there any limitation on how many tables I can export using DTS PKGS.? I have almost 110 tables, I need to export to another SQL server-- I want to use dts pkg-- is there limitation?
Thk
Josephine
ADVERTISEMENT
What To Do With Pkgs Once Created In BIS?
Mar 6, 2007Hi,
I have been in the process of creating some new pkgs in BIS. My question is, once I am done writing the pkgs, what next?
That is, how do I get the pkgs into SQL Server, and how do I schedule them to run?
Also, what if I have the following scenario:
I have created a new SSIS pkg that has several EXECUTE DTS 2000 tasks in them. The DTS packages that are called from the EXECUTE DTS 2000 task are stored in the database under "Legacy". These should still run OK once I "load" the packages to SQL Server 2005, yes?
Where do the SSIS packages "live" in SQL Server 2005? That is, where can I view them.
Thank you!!
Deploying SSIS Pkgs
Mar 14, 2007Hi,
I have some questions.
Regarding SQL Server deployment, it says to use this option if sharing packages between servers. Does this mean sharing packages between development, test, and production environments? Or just sharing among production servers?
That is, I am trying to determine if I should deploy my packages on SQL Server, or just store them on the local file system. These packages will NOT be used on any other production server. So should I just keep them on the file system?
Another question. I see that I have a package stored in the "sysdtspackages90" table in the msdb database. Since I have not done any SQL Server deployment yet, I don't understand how this particular package ended up in this table. Is it OK to remove? I think this is a previous version of a package that I have since re-written. Are there any dependencies on this "sysdtspackages90" table that I should be aware of?
Thanks!
SSIS Pkgs Migration Question
May 30, 2008
I have a server that is sql2000. We are planning to upgrade that to SQL SERVER 2005.
We also have a test 2005 server.
Before going live, we are migrating all 100 DTS pkgs that we have
in sql server 200 over to SSSS on the TEST 2005 sql Server. once all THE 100 DTSPKGS THAT we have in SQL
2000 PKGS Are scucessfuly migrated/tested on test 2005 server, only then we will
move forward with migrating the PRODuction 2000 Server to 2005.
My question is:
1. When we are ready to migrate PRODuction 2000 SERVER, TO 2005, We will need to transfer/copy all
the SSIS 2005 PKGS THAT WE HAD tested on the test 2005 server. Once we move that to prod 2005,
we will need to change datasource connection to point to the PRODuction 2005 SERVER.
However my question is WHAT IS THE EASIEST/FASTEST WAY TO tranfer/copy all these (100+ ssis pkgs)
2005 ssis pkgs that are on the TEST SERVER
OVER TO PROD 2005 SERVER? Do we transfer each and every SSIS PKg manually ,or is there any easy way to get
these 100 SSIS Pkgs, over from TEST 2005 TO PROD 2005?
Using Error Handler How Can I Execute My Pkgs If One Got Failed
Oct 24, 2006Hi Every one,
i give a small fuzzle for you here , ie . i have a job which includes 6 packages in that one and while running that job any one package is fialed how can i execute that next package even that before package was failed. i am using for loop container for running my 6 packages ... is there any method to do this like on error resume next in .net
sreenivas
Migrate SQL SERVER 2000 DTS Pkgs To SQL SERVER 2005
Nov 30, 2007
I currently have SQL SERVER 2000 Running. Once I upgrade that 2000 server to 2005, how do I migrate the dtspkgs that were on 2000 TO 2005?