How many times have you had to estimate space for a new SQL Server database? How much time did you spend on it? Was it a thumb-in-the-wind guess or did you actually examine a schema and calculate some values. If you have asked someone to estimate the space their database will need, they probably guess more than compute, but now Andre Vigneau gives us an easy way we can teach those developers to put some thought into the process.
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.
By Steve Jones
Next week is the 2024 PASS Data Community Summit in Seattle. I’ll be traveling...
By Steve Jones
bye-over – n. the sheepish casual vibe between two people who’ve shred an emotional...
I’m hosting a free webinar at MSSQLTips.com at the 19th of December 2024, 6PM...
Hello everyone, I hope you can help me. I have a table with measurement...
You can't handle the truth!! (about data integrity) A few good database administrators https://www.helpmasterpro.com/blog/a-few-good-database-administrators/...
I have installed Machine Learning with SQL 2022 Enterprise Edition and installed and configured...
I have run this on SQL Server 2022 for the Sales database:
ALTER DATABASE Sales SET AUTO_CREATE_STATISTICS ON (INCREMENTAL = ON)I then run this in the Sales database:
USE Sales GO CREATE STATISTICS CustomerStats1 ON dbo.Customer (CustomerKey, EmailAddress) WITH INCREMENTAL = OFFThe dbo.Customer table is partitioned. How are statistics created? See possible answers