Why are two databases created when I build?

Question

I'm new to VS DB Edition.  I've toyed around with it for a couple days now, and I'm confused about something.  I may be going about the process all wrong, so please bear with me.

I create a DB project, and I pull down a schema from an existing DB.  Next, I create a DB with the same name on my local instance, point my project at that DB, but when I build the project, it creates an additional DB - this one has a GUID attached to the end of it.

Can someone tell my why I'm getting two DBS?  Seems like I should only need one...

---

Clint

Answer 1

Clint,

Which version of the DB edition are you using? The additional DB with the GUID sounds like VS2005?

Thanks,
Joyce

Answer 2

It is VS 2008, but we are using SQL Server 2005 Standard Edition.

---

Clint

Answer 3

Is it VS 2008 SP1 without GDR?

If you don't have the GDR installed, it is normal to see the DB with GUID name. That is the design database we were using for design-time validation. We created the design DB when you create a database project. It is not supposed to be change by the users.

You do not need to (manually) create the DB on your target server, in your case, your local instance. The first time you deploy the database project, DB Pro creates the database for you. All following deployments will target to the same database, and only deploy the "diffs" to the server, if you don't change the target database name. 

Let us know if you have any further question on this. 

Thanks,
Joyce 

Answer 4

What is the best way to tell if I have the GDR version?

---

Clint

Answer 5

In VS main menu, check Help -> About ...

See if you can find Microsoft Visual Studio Team System 2008 Database Edition GDR in the list box.

Answer 6

thought so, just wanted to make sure.

I don't see it listed, so that must be my problem.

---

Clint