SSWUG Ultimate Virtual Conference – coming very soon!
Make sure you get registered – we have incredible content – great speakers, a whole lot of learning. All of it coming direct to your desktop. Put out the do not disturb sign, put your feet up and learn tips, tricks, best practices and techniques.
Can’t wait to see you there – [register here today]
Featured White Paper(s)
Managed .NET Connectivity
Database connections are the lifeblood of enterprise applications, administrating the secure and steady flow of information b… (read more)
SelectViews Show
SelectViews – Brent Ozar is on the show today, talking about all sorts of SQL Server issues, things from the field and yes, opinion.
I also sat down with the good folks from XKoto to talk about some of the really cool things they’re doing for SQL Server.
[Watch the Show]
Legacy Work-Arounds and SQL Server Upgrades
I’ve seen a couple of different consulting clients of late with a very similar issue that came as a bit of a surprise. They have systems currently in production and are looking to move these systems to the more current release(s) of SQL Server. No big surprises there.
What’s we’ve seen though is that several of these systems, coming from older SQL Server releases, are bringing forward work-arounds that were necessary in the older release, but not in current releases of SQL Server. I’ve seen this on several fronts, from index maintenance to maintenance plans in general to other procedures that were automated using very unique solutions.
The thing is, though, that in several cases, the work-around wasn’t needed any more. New updates to SQL Server, new functionality, new built-in native functionality, all combined to make the work-arounds obsolete, yet they remained in the upgraded database plan.
I tell you all of this just to say "make sure you check your systems and look for procedures that can be done more efficiently with the new target platform." Review automation, import, data cleansing and other routines. Are there things that are now better handled with native tools? Are other things in place that are no longer needed at all? Just be sure to review for these types of things, not just "what do I have to cut over to the new system" – but "what can I eliminate in the new system due to more core functionality?"
Food for thought on this Monday.