Visual Studio Team System Database Edition Best Practices

SQLServerPedia Syndication, Visual Studio
Barclay Hill, Program Manager for Visual Studio Team System Database Edition at Microsoft has just launched a new blog that I'm excited about. He's going to be blogging on best practices for VSTS:DB. His initial post outlines the topics he hopes to address and it's an impressive list. I responded immediately with an offer to help because I'm using the tool and struggling a bit to get it to do everything we need and because I really like all that VSTS:DB has done for me and my team already. Any one else interested in pitching in should go over there and get involved. Here's what I sent as an initial message: I saw your blog post and request for interest and participation and decided to pitch in. The company where…
Read More

Finally, the GDR is Released

Visual Studio
From the Data Dude himself. This is great news. I've been working with the CTP's for several months now, telling the other DBA's on my team that they had to wait until it was completely ready for release. It's been a long wait, but I'm sure it's worth it. My congratulations to the team. I met several of you at the PASS Summit. I really apreciate the work you've put into this great tool. It really makes a difference in how we develop and deploy databases. The changes in the GDR are making a great utility even better.¬† Thanks Mr. Drapers. Thanks also to Jamie Laflen, especially for helping validate some of the ideas I presented at PASS. Thanks to all the rest of the team, whose names I don't…
Read More

VSTSDBE RC0 Post 3

Tools, Visual Studio
Second round of testing. Instead of associating with a project, I tried creating a reference to a .dbschema file. Same error. This time, I'm going to clear out everything. I tried creating it initially on top of the code from CTP 17. So, another chance to try out the reverse engineer process of "Import Database Schema." Works great. New AdventureWorks database inside Visual Studio with a tested deployment faster than you can spit. Created a new server project. Added a login, just to give it something to do. It deployed fine. On to the compound project. Let's see what happens. Just to see, I did a build and deploy before I added references or objects or anything. It worked great. Whatever that means. I'm taking it a step at a…
Read More

Benefits of a Tear Down & Rebuild in a Database

Tools, Visual Studio
Using the Team Edition of Visual Studio for Databases (VSDB)¬†enables you to build a database out of source control. This means you can treat your database like code, as much as you can. The fact is, because of persistence, a database just isn't code. Because you have to keep all the data previously entered, when you deploy a new version of your database to production, you don't simply get to replace the database like you do with the code. You have to run scripts that alter that which can be altered, but preserve the existing data everywhere. That's just how it is in production. You have to do the work necessary to protect your data. Not so in Development. Development (and QA, Test, Financial Test, Performance Test) is the place…
Read More

VSTS 2008 Database Edition GDR: Still More First Impressions

Tools, Visual Studio
Following on to my adventures in creating multi-environment deployment processes with the new version of Data Dude (DBPro, VSTS Database Edition, whatever we're calling it this week). I've create a new configuration, copying all the settings from the Debug configuration. I'm adding a new Deployment configuration file and making a change. The deploy worked. Woo hoo! Now to get really funky. I'll create a new "Sql command variables file:" and add a variable for setting the data directory. Now to deploy and... Urk! Failed. It's not recognizing my variable. Now I'm stuck. I've checked the syntax. It's right. I double checked it all and reran deploy. Now it works... Color me confused. Whatever. Successful test. Time to create another configuration, simulating a QA server... Got that working too. I don't…
Read More

Microsoft Connect and DBPro Enhancement

Visual Studio
I've mentioned it before and I think it's worth mentioning again, Microsoft Connect really works. I've seen bugs and enhancements listed there receive enough attention that they were in the next release or service pack of the product in question. That brings me to DBPro. We use DBPro for all our database development. It's a great tool. However, it's still a bit to geared toward the individual user and not the team, despite it's moniker (Visual Studio Team Edition for Database Professionals). One thing that really does bother me is how it stores some settings, such as Target Connection in the .user file within a project. This means that each individual sets the connection for the project each time they check it out after another user has had it. Another…
Read More