Back Yourself Up
Ever thought about yourself as a resource that should be backed up to minimize your loss?
2018-09-05
91 reads
Ever thought about yourself as a resource that should be backed up to minimize your loss?
2018-09-05
91 reads
What makes SQL Server professionals stick together? Can we draw any conclusions from this?
2017-07-10
133 reads
Both options have their advantages and disadvantages. Neither is universally right for all situations. Understand the differences before picking the model that works for your situation.
2017-06-12
12,194 reads
Are you a do-it-all DBA, or do you specialize in one aspect of database work?
2015-09-07
308 reads
One Way to Handle a Very Complex Database Project with Several Databases and Cross References
2015-05-19
12,091 reads
2013-07-26
611 reads
A table does not so much 'have' a clustered index as a table 'is' a clustered index.
2013-07-22
6,514 reads
An introduction to Universal Product Codes with code to help you use them in your database.
2013-02-28
6,595 reads
A table doesn't so much "have" a clustered index as a table "is" a clustered index.
2012-12-24
8,370 reads
Today we have a guest editorial from Hakim Ali. Today Akim talks about why holding back out of politeness in code reviews may be a self-defeating practice.
2012-08-06
355 reads
By Steve Jones
I needed to test a striped backup, so I decided to ask the AI’s...
By gbargsley
In SQL Server environments where transactional replication runs alongside Always On Availability Groups (AGs),...
Disable the sa login in SQL Server (and sleep better)If you run SQL Server...
Comments posted to this topic are about the item Create an HTML Report on...
The SQLPS.exe file has gone AWOL on 2 of my 4 SQL servers, ie,...
Comments posted to this topic are about the item Be Wary of Data
You have a table [dbo].[orders] without a Clustered Index (Heap). The table does not have any other nonclustered indexes! You rund the following command in Read Committed Isolation Level:
SELECTo_orderdate, o_orderkey, o_custkey, o_storekey FROMdbo.orders WHEREo_orderkey = 3877;