Detailed error reporting from stored procedures can be extremely valuable when debugging problems in your application. I will share different levels of detail that you can build into your stored procedures. You can choose the level of detail appropriate for your situation.
SQL Server does a wonderful job of tuning itself, selecting the optimum query plans and in general performing very well under a variety of conditions. That does not mean the a good DBA cannot add value by setting up the system and ensuring the optimizer receives the information that it needs. New author Gordon Pollokoff brings us a short case study from a project he as recently involved in where a new application required a bit of tuning.
SQLServerCentral.com is having a sale. Support the site and get some valuable information for your library.
Table partitioning is a powerful new feature in SQL Server 2005. It is primarily a manageability feature, but my interest here is in the performance and scalability of table and index partitioning for use with very large tables.
This is a two part series on how triggers work in the two latest versions of MS SQL Server. Because there are some pretty significant additions in trigger functionality from 7.0 to 2000, we'll first need to look at what the two versions have in common. The second part to this series will look at the differences between the two MS SQL Server versions.
Databases are being stolen. Customer data, credit card data, taxpayer data - they're all vulnerable. Scary? Yes - but wait, there's more. It's not just "their" data that's vulnerable - it's ours too!
Chris Hedgate, one of our regular SQL Server columnists, recently became intrigued by the way that SQL Server implements the week number. His concern was why SQL Server treats week 53 as week 1, which is not that way that ISO6801 sees it. Read about his investigation into the methods of implementing an algorithm to solve this problem.
Fabian Pascal, famed database author and writer takes his shots at a recent thread on another SQL site. He makes some good points about normalization.
SQL Server 2005 has added a new format for queries called a Common Table Expression or CTE. CTE’s are part of the SQL:1999 Specification and represent further compliance with this specification by SQL Server. This article will cover using one of the many capabilities of CTE’s, implementing recursive functions. A recursive function is a one that iteratively executes itself. Understanding how CTE’s implement recursive functions is the first step to understanding the full capabilities of CTE’s.
Robert Pearl of Pearl Knowledge Solutions, Inc., recently attended a meeting of the NY Database Professionals Council where SQL Server Analysis Services 2005 was a large part of the topic of conversation. Read his report on the push to move business intelligence into the mainstream.
By Steve Jones
dorgone– adj. wondering if you could slip away from an event or group conversation...
By ReviewMyDB
Many of us use AI the same way every single day. Open a tab....
By SQLPals
SQL Server Transaction Log Forensics: Preserving Evidence During an Incident SQL...
Could you please let me know if anyone is used https://github.com/ktaranov/sqlserver-kit github for deployment...
I’ve been looking into ways to improve the connection between a website and its...
Comments posted to this topic are about the item When And How to Automate?
How many Azure SQL DB Hyperscale HA replicas can be configured as of Sept 2026?
See possible answers