Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jpham
Starting Member
19 Posts |
 Posted - 2007-01-17 : 17:38:48
|
| Hi All,MSSQL 2005 is released and we would like to leverage the new features of MSSQL 2005 to improve the performance of our application whichhave been written using MSSQL 2000 transaction SQL.I don't whether any one of you have done some researches onthe new features of MSSQL 2005 that can be use in our application that can improve the performance. I only knew the "Table Partitioned"is the new feature of MSSQL 2005 that we can leverage our application to use this new feature to improve the performance.Any other features of MSSQL 2005 that can be used to improved theperformance.Thanks In Advance,JP |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2007-01-17 : 19:55:25
|
| First port of call should be to lookj at the way the current queries are coded - see if they could be improved or structures changed to support them.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
LoztInSpace
Aged Yak Warrior
940 Posts |
Posted - 2007-01-18 : 23:57:17
|
| Not that I've used it (so take this with a grain of salt) but I would say that turning on the new "row versioning" would help a lot. This essentially prevents write locks blocking readers. In itself it won't make your queries run any faster but it has the potential to make your database really fly if you have loads of users - especially with mixed loads of running reports and updating stuff. Oracle works like this and it pisses all over other databases in this regard - massive throughput because only write contention causes blocking.I'd research it yourself to see if you need it. The only downside I can see is that if you have an application that does some wierd process control using rows in a table, that would not work. Also (probably - I'm guessing a bit here) your selects would return the data as at the time the transaction started, where as now, with blocking, you get the data as at when all the blocking transactions commit.Random link:http://msdn2.microsoft.com/en-us/library/ms345124.aspx |
|
|
|
|
|
|
New Feature of MSSQL 2005