January 21, 2009 at 1:36 pm
I just installed a developer addition of SQL Server 2008 on my local machine at work. Work still uses 2000 for their databases.
I want to work within the 2008 Environment, so I wanted to create a job to import the core tables from the other systems to the one on my system.
I went through the import wizard and was able to import the tables, but what I would like to do is to save the import process as SSIS package and schedule it (to truncate and repopluate these tables on my system with the most recent data) to run durring out companies down time.
January 21, 2009 at 2:01 pm
As long as you use developer edition you can either check the save package at the end of the Import data wizard and create a file. Or using visual studio you can start a Integration Services Project (SSIS) and use the copy object tool to set up an import from the main database. You can also use the connections to build a customer loader if you only need to test portions of the data. I would recommend that you keep them as files for now as they are easier to manipulate and share. You will have to make a choice later whether to store them as files order in the SQL server.
To run the package you can either:
1. Use scheduler to run the packages using dtexec on the command line
2. Use the SQL Agent that can be installed with developer edition. I believe that it installs by default but you can use the install disk to add it.
Note that SSIS will only run on servers with developer, enterprise, and standard edition.
January 22, 2009 at 7:02 am
Thank you for the quick response.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply