Dev. to Testing Best Practices

I am looking for ideas on how to move changes made to a database structure (e.g. sprocs, udf, views, tables) on the development machine to the testing server without affecting the data on the testing machine.
The developent server and the test server are on separate networks.
Thanks,
ROB
--
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.> without affecting the data on the testing machine.
What changes to the structure are going to affect the data? Could you be
more specific about what structure changes you are talking about?
Typically, we generate DDL scripts (CREATE PROC, ALTER PROC, ALTER TABLE,
etc.) and run them on the target server. In most cases, we do this in
conjunction with a source control tool.
What kind of "best practices" are you looking for? Minimum downtime,
maximum security, etc.? I don't really think there is a "best way" to
deploy database changes, but depending on your goals, they might make you
lean one way or another.
--
http://www.aspfaq.com/
(Reverse address to reply.)