|
Home > Archive > MS SQL Server > November 2006 > Scripting the DB in VSS
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Scripting the DB in VSS
|
|
|
| Scripting the database and then loading it into Visual source safe for
versioning seems like a very good method of managing the different versions
of the DB used in the production environment. I noticed that the script has
produced the DB without the data in it. I don't see an option in the
scripting wizard to include the actual data (both 2000 and 2005). I
understand that including the data is unrealistic especially when the DB size
is significant. Nevertheless, what is the best method to manage the data to
coincide with the version of the scripted DB that is stored in sourcesafe?
Thank you.
| |
| Hilary Cotter 2006-11-10, 12:12 am |
| try this
http://www.brentozar.com/archive/20...ual-sourcesafe/
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"mmc" <mmc@discussions.microsoft.com> wrote in message
news:C155B6C7-7D7B-4C77-BA9B- 1D56CA4AE43D@microso
ft.com...
> Scripting the database and then loading it into Visual source safe for
> versioning seems like a very good method of managing the different
> versions
> of the DB used in the production environment. I noticed that the script
> has
> produced the DB without the data in it. I don't see an option in the
> scripting wizard to include the actual data (both 2000 and 2005). I
> understand that including the data is unrealistic especially when the DB
> size
> is significant. Nevertheless, what is the best method to manage the data
> to
> coincide with the version of the scripted DB that is stored in sourcesafe?
> Thank you.
| |
| Hilary Cotter 2006-11-10, 12:12 am |
| Sorry, I misread your post. You can store a back in vss, or you could bcp
the data out.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"mmc" <mmc@discussions.microsoft.com> wrote in message
news:C155B6C7-7D7B-4C77-BA9B- 1D56CA4AE43D@microso
ft.com...
> Scripting the database and then loading it into Visual source safe for
> versioning seems like a very good method of managing the different
> versions
> of the DB used in the production environment. I noticed that the script
> has
> produced the DB without the data in it. I don't see an option in the
> scripting wizard to include the actual data (both 2000 and 2005). I
> understand that including the data is unrealistic especially when the DB
> size
> is significant. Nevertheless, what is the best method to manage the data
> to
> coincide with the version of the scripted DB that is stored in sourcesafe?
> Thank you.
| |
|
| Let's say I am rolling out from the Dev server to the Prod server. How do you
deploy the DB? Options are to restore, attach, or script? Let's say I choose
"script". I check out the latest script version from VSS and then run it.
Next question is how and where would I pull the data to load into the DB?
With restore or attach, all I have to do is point to the path of the .mdf .
Does it mean that after I script the DB out to VSS, I would also have to BCP
the data separately each time?
"Hilary Cotter" wrote:
> Sorry, I misread your post. You can store a back in vss, or you could bcp
> the data out.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
>
>
> "mmc" <mmc@discussions.microsoft.com> wrote in message
> news:C155B6C7-7D7B-4C77-BA9B- 1D56CA4AE43D@microso
ft.com...
>
>
>
|
|
|
|
|