Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
gchacko
Starting Member
8 Posts |
 Posted - 2002-08-20 : 16:18:14
|
| I created a DTS package to transfer data from a flat text file to SQL Server table. Tested the package within the designer.How can I implement the package in Production.Please give the steps.Thanks in advance |
|
|
KHeon
Posting Yak Master
135 Posts |
Posted - 2002-08-21 : 07:24:08
|
| Assuming that your development and production servers are the same version (SQL Server 7 on both, or SQL Server 2000 on both). The easiest way to do this is open the package on your development server and do a "Save As" on it. In there you can choose where to save it, including the server (just select the server in the Server dropdown).If the versions of SQL Server are different though you will have issues. Going from SQL Server 7 up to SQL Server 2000 shouldn't be a problem but the other way you could have issues because not only is there new functionality in SQL 2000 the file formats are different (unless you are running SQL Server 7 SP3, then they are the same). There are ways around that however.If this doesn't solve you issue, please post more information (ie: SQL Server version information).Thanks!Kyle HeonPixelMEDIA, Inc.Senior Application Programmer, MCPkheon@pixelmedia.com |
 |
|
|
gchacko
Starting Member
8 Posts |
Posted - 2002-08-21 : 09:16:02
|
| Thanks for the info.The plan of saving the package to different will work.But that doesn't suit our IT statndards.The test and production are on different boxes running same version of SQl Server. But the deployemnt has to be done thru "running scripts". Just the way we do for deploying a database or table.Any ideas. |
|
|
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
Posted - 2002-08-21 : 12:32:43
|
You could certainly write your own script that moved the appropriate rows from the msdb database for your package. That is an effort-intensive and unnecessary process, though - Kyle's suggestion is much better.Also, make sure that you have properly updated any server references inside your package. Moving the package to your production server doesn't in itself guarantee it will access your production server  .Jonathan Boott, MCDBA{0} |
|
|
|
|
|
|
DTS Deployment