Conversation History: The Continuing Case Against GUIDs
We had a cooperative relational database design exercise at the office last week as part of our regular department "Lunch...
2013-03-08
1,222 reads
We had a cooperative relational database design exercise at the office last week as part of our regular department "Lunch...
2013-03-08
1,222 reads
I had a project recently where I had to do math on a number that represented a date, YYYYMM.
For example,...
2013-03-01
665 reads
In SQL Server Reporting Services, when adding a new dataset to a report, you may see an error that looks...
2013-02-28
8,223 reads
It's easy enough to use sys.foreign_keys and sys.foreign_key_columns to identify foreign keys. But what if you want to script out your foreign...
2013-02-18
1,175 reads
Here's a script to determine, based on your database's foreign key relationships, what the insertion order would be for, say,...
2013-02-17
1,519 reads
Of course, a rather obvious answer presents itself the next day. After reviewing the actual environment that my colleague was...
2013-02-05
710 reads
A colleague of mine was understandably confused when using the almost-perfect missing index engine in SQL 2008. The engine recommended he include...
2013-02-04
675 reads
Tried something different for the January 2013 meeting of the Baton Rouge SQL Server User Group (brssug.org), which meets every...
2013-01-10
952 reads
If you're working in an environment as a developer without sysadmin privileges, and you are creating database diagrams using Management Studio...
2012-12-10 (first published: 2012-12-03)
3,255 reads
Starting with SQL 2008, we database developers started becoming more familiar with datetime2. Sometimes folks need convincing though, so here...
2012-12-04
12,254 reads
By Steve Jones
This is my last week of the year working (I guess I come back...
By Steve Jones
suente– n. the state of being so familiar with someone that you can be...
Anyone (everyone?) who has ever tried to learn a programming language knows that to...
I am getting the below error when I execute a SQL command in SQL...
I am getting the below error when I execute a SQL command in SQL...
Hi everyone. I have this table and this information. (left side of the image)...