March 12, 2009 at 2:45 pm
Hi Everyone
I'm about to move our existing 32 bit databases to a new 64 bit server and must have exactly the same setup.
All SSIS (12) packages must also work properly so i created this checklist.
SQL Server 2005 SE SP2
3 databases totaling 520GB.
1. Recreate Domain users and groups
2. Move SQL Server Logins
3. Move databases (backup/restore)
4. Exec sp_change_logins to link users with logins
5. Move SSIS packages and all the config files (our packages are stored in the file system)
6. Move scheduled jobs associated with SSIS packages
7. Test SSIS packages.
8. Recreate maintenance jobs (rebuild index, full tran log and differential backups.
I just hope i don't get these errors:
I did read IS considerations on 64 bit computers document:
http://msdn.microsoft.com/en-us/library/ms141766(SQL.90).aspx
Our SSIS packages use SOAP to interact with a 3rd party app. I spoke to their support team and they said everything will run smoothly. I guess i will find out in step 7.
Has any of you done this in the past? what should i expect?
Any help appreciated
March 12, 2009 at 3:30 pm
If you have Office packages you must run the SSIS x86 that is 32bits directory to execute your code because there is no 64bits Office driver. I can help with many platform related issues but I usually ask you tell me source and destination so we can resolve your issue quickly or look for how to resolve it. When you are using Web Service it is better to use Windows 2008 so you could run IIS 7 in both 32bits and 64bits mode as needed.
Kind regards,
Gift Peddie
March 12, 2009 at 3:41 pm
As the previous post mentioned, i had some trouble connecting to Excel when i migrated a server to 2005 64 bit...Jet drivers are not supported on 64 bit.
One more thing, to avoid having to fix sids and things you could use the sp_revlogins sciptie to move the logins between servers...http://support.microsoft.com/kb/918992 could be useful
Gethyn Elliswww.gethynellis.com
March 12, 2009 at 5:54 pm
Gift Peddie & Ellis
Our SSIS packages interact with a 3rd party ETL tool called DataLever which cleans and then loads all the data from 16 different sources into a Staging database triggering SSIS via SOAP.
SSIS takes over and after a few finalizing (business rules) steps loads the data into the production db.
If there is an error SSIS starts error specific ETL processes to filter sources that produced the error and emails appropriate personnel. Erroneous sources go into another database for review.
Packages run 24/7 so i will have to parallel test for a few days.
Thanks for the heads up i will use sp_revlogins.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply