http://www2.sqlblog.com/blogs/merrill_aldrich/archive/tags/Migration/default.aspxTags: MigrationenCommunityServer 2.1 SP2 (Build: 61129.1)http://www2.sqlblog.com/blogs/merrill_aldrich/archive/2010/04/22/server-migration-checklist-ii.aspxFri, 23 Apr 2010 05:18:08 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:24523merrillaldrich0http://www2.sqlblog.com/blogs/merrill_aldrich/comments/24523.aspxhttp://www2.sqlblog.com/blogs/merrill_aldrich/commentrss.aspx?PostID=24523Easy Breezy Login Audit for your Ol’ 2000 Server In the last post on this topic I put up the preparatory steps I’ve been using for server migrations. Here I am posting some code that has worked well for us to trace who/what is connecting to our older...(<a href="http://www2.sqlblog.com/blogs/merrill_aldrich/archive/2010/04/22/server-migration-checklist-ii.aspx">read more</a>)<img src="http://www2.sqlblog.com/aggbug.aspx?PostID=24523" width="1" height="1">Migrationhttp://www2.sqlblog.com/blogs/merrill_aldrich/archive/2010/04/09/server-migration-checklist.aspxFri, 09 Apr 2010 22:26:39 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:24185merrillaldrich2http://www2.sqlblog.com/blogs/merrill_aldrich/comments/24185.aspxhttp://www2.sqlblog.com/blogs/merrill_aldrich/commentrss.aspx?PostID=24185During the past six months or so I have had to manage quite a lot of SQL Server migration/consolidation, and with each effort I’ve refined a checklist to try to make things go more smoothly. I just hate getting that call after a migration where something...(<a href="http://www2.sqlblog.com/blogs/merrill_aldrich/archive/2010/04/09/server-migration-checklist.aspx">read more</a>)<img src="http://www2.sqlblog.com/aggbug.aspx?PostID=24185" width="1" height="1">Migration