we upgraded our mom warehouse infrastructure to utilize sql 2005 before the official article was released using the three separate articles i had posted earlier. so far, successful. all dts packages execute post-upgrade! big benefit for me? i can use vs2005 to write the reports now. time to move on to upgrading the production databases. anyway...
since that time, microsoft has released an official knowledgebase article on the issues/hotfixes regarding upgrading to sql 2005.
UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress. if you are using the v2 toolkit, PLEASE read this blog post before proceeding. here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can
Comments
Post a Comment