January 6, 2011 at 10:58 am
Hello
We are planning to move our production database to a virtual server. Both database servers run SQL Server 2008. We have between 30-50 SSIS jobs on our server.
With respect to SSIS Jobs in particular, we would like to know whether anyone has done this before and what are the recommended approaches to moving SSIS jobs in particular?
To maximize success of our project, our goal is to avoid recreating SSIS jobs and to limit the scope of work to changing connecting strings that point to the new database server.
My understanding is the jobs are stored in the master database, but would like to know to whether additional scripts have to be run to extract SSIS job information or if in fact moving the database alone is sufficient to moving the jobs.
Thanks in advance for any feedback.
Anthony
January 6, 2011 at 11:11 am
move all ssis packages manually n change the connectionstrings for each ssis package, n for jobs... script out all jobs on a single file....replace server name by using replace-all option n execute dat script....
also take a look at this thread
http://www.sqlservercentral.com/Forums/Topic571634-148-1.aspx#bm571868
January 6, 2011 at 11:31 am
Are you not doing a P2V conversion?
Moving to a virtual server is no different than moving to a new physical server. The underlying architecture doesn't really matter to SQL Server. Script them, save/load, whatever you would do to move to a new physical server is what you would do.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply