Migrating to SQL Server 2012, a tale of trial and error, part 2
My migration to SQL Server 2012 has actually been going rather smoothly. The other issues apart from the one I discussed earlier have been relatively minor, although some were time consuming to work out and some were annoying. Here is what I have run into so far:
- VSTA did not install correctly. I had to uninstall VSTA and then repair SQL Server 2012 before I could edit SSIS scripts, and it has happened on three different workstations so far.
- The VS 2010 source control “output” window goes crazy at times with TFS 2010 error messages, particularly if the main window is empty.
- Not all SSIS components migrated properly. I have lost track of the details, but nothing was especially hard to fix. For the most part the migration was clean.
- My geocoder custom SSIS component isn’t compatible (yet). That part of the migration didn’t work.
- The VS 2010 Server Explorer window can only show data from SQL Server 2012 databases. It can’t create, modify, or delete SQL Server 2012 objects.
- The new VS 2010 SQL Server Object Explorer window (part of SSDT) did not show up in the view menu of the stand-alone version of SSDT installed with SQL Server 2012 (when Visual Studio is not already installed).
- For some reason the ctrl-R shortcut disappeared from SSMS on one of my workstations. I use it a lot and want it back! (It hides the results pane after running a query).
- Database references are apparently not implemented in the SSDT version of Database Projects (you can declare them but they don’t do anything), and VS 2010 Database Projects do not support SQL Server 2012, so I am having to do without them for now.
As you can see, these issues are minor but mostly unresolved. If I come across any solutions I will post them here.
Updates (5/7/13):
- Fixing the SSMS keyboard shortcuts was really easy — there’s a “Reset” somewhere in the menus that will do just that (wish I remembered where I found it)
- Database references work great in SSDT database projects, once you know the trick.
- Despite what I said above, one of my SSIS script components stubbornly refused to migrate. The problem was that it used .Net Framework 2.0 “web references” that are not supported in SSIS 2012. The obvious fix — rewrite to use WCF “service references” instead — didn’t work because the service referenced is MS CRM 4.0 and there is an incompatibility. In fact, Microsoft said it just plain doesn’t work. That isn’t actually true, fortunately, but it took a large amount of effort to figure out, and a fair amount of time to re-write the component, and I will be describing what I did in a future blog post.
Comments
Migrating to SQL Server 2012, a tale of trial and error, part 2 — No Comments
HTML tags allowed in your comment: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>