Database corruption can be difficult to detect and sometimes it is very possible that you might not even notice it until you run DBCC command on your database to check logical and physical consistency of that database. It is very common practice to run DBCC CHECKDB without any additional options at regular intervals to make
Category: SQL Server
Issue with Backup sets of Backup in SSMS 2012
Just like many fellow early adopters, me too have installed shiny new SQL Server 2012 in my work machine. And I have been using it quite a while. Since it is “Powered by Visual Studio” now it has look and feel of VS 2010 too (for me main reason was included support of BIDS …
Adventureworks in SQL 2012
After trying different RCs, finally this weekend I got time to download SQL 2012 rtm dev edition from my dreamspark account. And my first decision was to get some test dbs with some nice data. And choice was pretty simple, use Adventureworks sample databases from CodePlex. But with a bit of surprise, they don’t have
Isolation levels in SQL Server … part II
In previous post I explained basics of ISOLATION levels in general. This post is a sort of demo of isolation levels in SQL Server. In SQL Server, Isolation property can be configured using “SET ISOLATION” command. This command can be used to set isolation at any given transaction. SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED GO
Isolation levels in SQL Server … part I
Just like any reliable transaction system, SQL Server supports ACID properties. If you have never heard of ACID properties before than it is actually set of four properties Atomicity, Consistency, Isolation and Durability. These set of properties makes sure that what ever transaction we do in SQL Server (or any DBMS) and database performs consistently
Resolving … Agent XPs disabled issue in SQL Server 2005
SQL Server sometimes behaves very strangely for no apparent reason. Few days back I was playing with our staging server and I had to stop SQL Server service for some testing purposes. When I started it back, I saw that SQL Server Agent was disabled and next to it a message showing that “Agent XPs
“EXECUTE AS” clause in T-SQL
In T-SQL there is really interesting clause available which allows DB engine to execute some particular module (function, SP, trigger etc) with context to some user. This clause is very handy when we don’t want some specific user to have access to some schema but we still want that user to allow access to data