TinyInt, SmallInt, Int and BigInt
SQL Server guru David Poole takes a look at the different integer data types and the impact of each of those on your database.
SQL Server guru David Poole takes a look at the different integer data types and the impact of each of those on your database.
An exploration of the process of translating a conceptual model to a logical model, and ultimately, a faithful implementation using T-SQL.
In this sample chapter, William R. Vaughn gives you a kick-start on designing relational databases that can perform better, be easier to maintain, and be more successful thanks to a combination of formal rules and informal suggestions to normalize your database.
This Workbench is about using Regular expressions with SQL Server via TSQL. It doesn't even attempt to teach how regular expressions work or how to pull them together. There are plenty of such resources on the Web. The aim is to demonstrate a few possibilities and try to persuade you to experiment with them if you don't already use Regex with SQL Server.
What do IT workers want for Christmas? Let us know in this Friday's poll.
Most SQL Server programmers know to use the SET NOCOUNT command to prevent the number of rows message from being returned to the client. But how does this affect performance? Does it make sense to qualify the owner on your objects? SQL Server guru David Poole brings us some performance analysis of how your stored procedures perform.
Visa has developed Payment Applications Best Practices and will begin implementing mandates concerning them
When we talk about something being reliable, we're referring to it being dependable and predictable. When it comes to software, however, there are other key attributes that must also be present for the code to be considered reliable.
Storing sensitive data in your database leads to security risks. Learn how not storing sensitive data indefinitely is a form of data protection.
Cell phones are great communication tools, but that's mostly what they do, even for IT folks. But Steve Jones talks about some other possibilities and potential problems.
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers