SQL Server Diaries

During a recent database migration I encountered strange behaviour when scripting out views, stored procedures and triggers. The issue was reported by the development team who noticed that object code lines were being split into two lines. After fixing the objects affected by this problem I investigated the cause and... [Read More]

When developing application code it is always recommended that all source code is backed up, preferably using a version control application to allow for code sharing and providing a change rollback. Using a tool such as SQL Server Management Studio, a developer can store database code developed with SSMS in... [Read More]

A while back I wrote a short post about the tablediff.exe command-line application. As a quick reminder, the tablediff.exe utilty can be used to compare table schema and/or data and generate a T-SQL script which can be used to bring the two in sync. [Read More]

SQL Server supports two authentication mechanisms, namely Windows and Mixed Mode. In Windows Authentication only accounts created on the local machine or domain accounts (users, groups, etc.) can be granted access to the SQL Server instance. This is the preferred and recommended (by Microsoft and most DBAs) implementation since the... [Read More]

Restoring databases is quite simple, especially if you’re using the GUI.  Just right-click on the Databases “folder” in SSMS, Choose the “Restore Database” option and the interface will prompt you for the database name, from where you want to restore, and other parameters.  I prefer scripting though.  One reason is... [Read More]