August 25, 2009 at 6:51 am
Hi,
I am not so much after a list of why 2005 is better i.e. its 64 bit so no AWE over heads etc...
But rather what things to take advantage of i.e. on a 24 hr system implementing online indexing will prevent any blocking happening.
Any thoughts?
Many thanks
August 25, 2009 at 7:54 am
A few things like better connection pooling and multiple active result sets (mars) [need to upgrade to SQLNCLI], better management tools [and better interface i think]in SSMC, better security granularity.
But there is really not a whole lot without changing some of your application (code and architecture) to take advantage of all of it. If you are willing to do that you can make some nice improvements in performance.
That's my story and I am sticking to it.
The probability of survival is inversely proportional to the angle of arrival.
August 25, 2009 at 8:34 am
Are you talking upgrading from SQL 7/2000 to 2005? Or 32bit to 64?
August 25, 2009 at 9:03 am
sorry db has gone from 2000 to 2005 so no justification is needed. All I want is to insure that as a DBA I am making the most of the new features. Many thanks
August 25, 2009 at 9:13 am
I'd be sure that you are running 2005 code and are in compat mode 90.
However from there what you might want to do is refactor code where you can to take advantage of new T-SQL features. Some of them are more efficient. I'd go through a perf tuning exercise. Look for the bottleneck queries, check execution plans again, and see what you can improve.
Move to 2005 features, like DBMail instead of SQL Mail.
Lots of enhancements in the engine itself that you get for free.
August 25, 2009 at 10:09 am
Thanks online indexing was about the only thing I could think of. Many thanks
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply