Contact Us

In many cases, while we using DBCC commands, we must to run two statements instead of one, in order to receive the wishful result. For example, in order to receive database information, we write: DBCC TRACEON (3604); GO DBCC DBINFO (‘AdventureWorks2012’); GO instead of simple: DBCC DBINFO (‘AdventureWorks2012’); GO So, why we need to use additional statement, why we enable trace flag 3604 before part of the DBCC commands? The answer consists of two parts: 1. Most of the trace

In SQL Server, when we use the “WITH SCHEMABINDING” clause in the definition of an object (view or function), we bind the object to the schema of all the underlying tables and views. This means that the underlying tables and views cannot be modified in a way that would affect the definition of the schema-bound object. It also means that the underlying objects cannot be dropped. We can still modify those tables or views, as longs as we don’t affect the definition of the schema

Last week, Boris Hristov (b|t), the organizer of #SQLHangout, invited William Durkin (b|t) and me to a SQL Hangout about transitioning from being a DBA to being a consultant. We had a great conversation and covered a lot of issues. Among them: What skills are important as a consultant In what ways being a consultant is different, and in what ways it’s the same What complex situations you might face, and how to tackle them Interesting projects each of us currently works on Bod