Here we go, the second week of The Best SQL Server Links Of The Past Week series.
It was a slow week this week, didn’t see a lot of things
Linchi Shea’s three-part post about performance impact with file fragmentation andthe SAN
Alexander Kuznetsov explains that it is well known that UPDATE … FROM command does not detect ambiguities. Also it well known that ANSI standard UPDATE may perform very poorly and may be difficult to maintain
Podcast: Ryan Dunn – SQL Data Services (SQL in the cloud) (show number 42)
Greg Low’s podcast with Ryan Dunn about SQL Data Services. Microsoft Senior Technical Evangelist Ryan Dunn discusses SQL Services and SQL Data Services, the future of the cloud based data services, what is currently available and how to get started.
Do any of these error look familiar?
_[Microsoft][ODBC SQL Server Driver][DBNETLIB] General Network error. Check your network documentation
ERROR [08S01] [Microsoft][SQL Native Client]Communication link failure
System.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 – An existing connection was forcibly closed by the remote host.)
A significant part of sql server process memory has been paged out. This may result in a performance degradation.
Read Jason Massie’s post, also check out the link in the edit section
Madhivanan shows how to view the script of the DDL triggers
Nice post by Dan Guzman showing some code to get some details and the rowcount for partitions by using the DMVs
Indexing a bit column, that is just crazy talk…….or is it? Jason Massie shows some code which will make your decision if this is crazy or not really simple
The SQL CAt team published a paper named Diagnosing Transaction Log Performance Issues and Limits of the Log Manager
For transactional workloads I/O performance of the writes to the SQL Server transaction log is critical to both throughput and application response time. This document discusses briefly how to determine if I/O to the transaction log file is a performance bottleneck and how to determine if this is storage related; a limitation is due to log manager itself or a combination of the two. Concepts and topics described in this paper apply mainly to SQL Server 2005 and SQL Server 2008.
Bob Beauchemin writes “The “relational database bigots” I hang out with don’t like LINQ at all. They hope it would shrivel up in a corner and become part of the fad-technology graveyard. Or they’re waiting to make big bucks fixing the performance problems they think will ensue………….”
You can read the rest there and tell me what you think.
That is it for this week, I will tag the weekly posts with SQL Friday in case you want to see the whole archive in the future