The basic texts for developing SQL code tend to leave unsaid the basic techniques for building routines such as stored procedures in T–SQL. This article explains in detail how to develop things like that without the comfort of Visual Studio
To test SQL, you need test data. There are usually many reasons why you can't use production data. Although it is usually enough to use a utility to generate test data, sometimes your requirements will compel you to resort to code to supplement this. This article shows how he used SQL and C# to generate large volumes of test data involving related columns and complex distributions.
Alex Kozak discusses some general issues surrounding disk space requirements for SQL Server databases and shows how to estimate Disk space usage and requirements. He gives tips on using DBCC CHECKDB consistency check and for estimating the space required for replication
For application developers focusing on the needs of their code, rather than worrying about the complexities of data representation, the Entity Framework’s abstractions are essential. But eventually a database needs to be created, and this article shows how it’s done.
The Query Optimizer gets it right most of the time, but occasionally it chooses a plan that isn't the best possible. You can give the Query Optimiser a better idea by using Table, Join and Query hints. These come with a risk: Any choices you force on the Optimizer by using hints can turn out to be entirely wrong as the database changes with the addition of data over time.
This article introduces the concept of creating a Model within the Master Data Manager front-end, which will be the beginning of an example solution that will run for the rest of the article. Each of the different objects within the MDS object hierarchy will be covered, guiding the reader on how to build a model up step-by-step.
With a number of clients, I have been provided a sample format for a transactions along with instructions to develop a process to load it into a database as quickly and painlessly as possible. This usually comes with the requirements that the XML data file can have any number of records from 1 to n. This example demonstrates the most efficent and scalable way that I have found to solve this. Not to mention that it can be maintained without rebuilding the solutions each time the data format changes.