K. Scott Allen over at odeToCode.com has these three rules for developing with a database:
1. Never use a shared database server for development.
I’ve been preaching this one for years and hardly anyone will listen to me. Everyone has their own local copy so that no one stomps on anyone elses work. Duh! But, you think I can convince anyone?
2. Always have a Single, Authoritative Source for your schema.
Well, I guess if you all work off the same database, this isn’t an issue. But, if you all have a local copy. You’d better have one place you know has the real deal.
3. Version your database.
Absolutely. Other than scripting every change that is made, you have a reasonable way to do this? Scott says he does. Can’t wait to see it.
- Moving a SQL Database to 2005
I had a client call today asking how to restore a database from a backup made with SQL 2000 to a SQL 2005 server. Turns out, he was asking the wrong question. Most questions are like th...
- SQL For Programmers – ALTERing the TABLE
One of the main problems we seem to be stuck with at this point in programming history is, how do we version our databases? You could put the whole database into version control, I guess. Bu...
- MSSQL CREATE TABLE – SQL For Programmers
Once you have your database created, you'll want to get some tables set up into it. To do this, you'll need the CREATE TABLE statement that can be issued from the connection object once you've es...
- SQL For Programmers – Finding a String
Many times in our queries, we aren't looking for an exact match. We are looking for one string that exists in another. There are a couple statements available to us that will allow us to do this...
- SQL For Developers – 9 Reasons to bother
If you are a developer like I am, you've probably gotten by with pretty simple SQL for quite a while. In fact, my experience has been that developers don't get much past SELECT, INSERT, UPDATE, an...