career development
SQL Session – Inside SQL Server Policy-Based Management
If you're not already a member of the Charlotte SQL Server User Group, go now and sign up. This group is a great resource of knowledge
Latest
personal
Time to Bottle the Beer!
It's time to transfer the beer to the bottle! I tried a little of the premature beer. It definitely needs a little time in the bottle to mellow, and carbonate.
t-sql
ASC, DESC, and Filtered Views
I know I've covered quite a bit of the CREATE INDEX statement, but there is even more to learn. Today I want to cover ASC, DESC, and the WHERE clause for
personal
National Brewing Day
I've decided it's time to get back into brewing. So I went down to alternative beverage and get All the supplies to start crafting my own beer. I decided on
sql202
SET IDENTITY_INSERT
Let's say you have the following table on two servers, one in development and one in production. CREATE TABLE person ( personID INT IDENTITY(1,1) , firstName
sql202
Disabling Constraints
Constraints are great for maintaining the integrity of the data in your database. I'm not a big fan of running your database without them. It just opens up the
dev
SQL 202 – FILLFACTOR and Indexes
FILLFACTOR specifies the percentage for how full the Database Engine should make the leaf level of each index page during index creation or rebuild. FILLFACTOR
t-sql
Beginning Spatial with SQL Server 2008
I picked up this book as an introduction to the new geographic datatype in SQL 2008. I had played around with Google maps, and plotting WiFi hotspots I'd
SQL102
Referential Integrity
OK, I've talked about Primary Keys and Foreign Keys. Now let's talk about Referential Integrity. Basically this just means that any Foreign Key value in one
SQL301
SET TRANSACTION ISOLATION LEVEL
Like I've mentioned before, unless you use SET TRANSACTION ISOLATION LEVEL, the server will default to READ COMMITTED. What this means is by default, your
career development
SQL Session – DTS to SSIS
If you're not already a member of the Charlotte SQL Server User Group, go now and sign up. This group is a great resource of knowledge and connections to the
The Standard Stored Procedure: Why Every Proc I Write Starts With the Same 30 Lines
Every stored procedure I inherit tells me something about the engineer who wrote it. The ones with no error handling tell me they never had to debug a silent failure at 2 a.m. The ones with a bare EXEC sp_something and no transaction management tell me nobody ever