You work in a shop that puts business or application logic in SQL Server using stored procedures, views and functions to return values to the calling applications or perform tasks. This is not unusual for companies that use the SQL Server layer to perform
This tip aims to provide a description of Service Pack 1 for SQL Server 2012, including a description of the contents, the changes it makes to the SQL Server product family, identified bugs (and hotfixes to correct them), a description of the installation
You are a database professional considering or implementing a move to SQL Server 2012 from your current database configuration. You've heard horror stories about the SQL Server 2012 licensing model - double the cost, double the complexity. You need to fin
You, as a SQL Server data professional, are looking for ways to improve your queries. You've done the usual - avoided cursors and loops, used locks effectively, examined execution plans - what else can you tweak? Check out this tip to learn more.
This article is ideally suited to SQL Server developers and those data professionals wishing to know more about SQL Server functions, and wanting to get a greater understanding of which functions are available and how they can help improve the efficiency
Occasionally, new development work submitted from your developers (or indeed written by you, the data professional) can fail due to unforeseen execution errors. These errors are despite testing on your dev/test/QA platform. Sometimes these errors can be
Corrupt SQL Server databases are the worst nightmare of any SQL Server professional. In any environment, from small business to enterprise, the compromise of integrity and availability of the data can constitute a business emergency. This is especially t
Replication in SQL Server simply refers to the process of copying data from one database to another. This movement of data is subject to a large number of options configured at the publisher, distributor and subscriber, but for all the complexity it is su
New stored procedures or types, INSERT, UPDATE and DELETE transactions are being executed against your SQL Server databases by developers or other stakeholders on an ad-hoc basis, changing data without rollback plans, controls or an adequate audit trail.