Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
hasanali00
Posting Yak Master
207 Posts |
 Posted - 2005-03-22 : 06:18:38
|
| I am working on my first web development project. I have a shared space on a SQL server. However, for my development, i am working on my local server. My idea is that once I have tested my application, i will upload all the tables, SP and triggers onto my production sql server.However, I want to undestand HOW DO YOU WORK: when you guys a developing a database, do you first work on the local sql server and then upload the tables, SP, and triggers to the live / production sql server. OR, do you work straight on the productoin server.Thanks |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-03-22 : 06:59:51
|
| We have three server environments:Development - new stuff happens hereTest - The client can see this, and make their tests / acceptanceLive - No changes directly to this (well, "in emergencies maybe ... but")We "script" everything we do in Dev. For example, in Enterprise Manager Table Designer there is a button to "Script" the change. We NEVER save the table changes, we press the button and Cut&Paste the script into a "PATCH001.SQL" type file - sequentially numbered. Then we can re-run all the new PATCH scripts on Test, and eventually on LIVE.All our Stored Procedures are in individual files (we NEVER use RightClick Properties in Enterprise Manager). SO we just execute all the files with a modified date AFTER the last time we did it. (Actually each file contains a "Log me" SQL statement so that it is logged in the database, so we can query a specific database to see what version of a particular file we have run). Our Stored Procedure source code files also contain the "GRANT EXECUTE ..." permission statements.Kristen |
 |
|
|
hasanali00
Posting Yak Master
207 Posts |
Posted - 2005-03-22 : 07:17:12
|
| Kristen - everytime u answer my question, ur answers are full of new information. At the same time, i get depressed that i have a lot to learn yet about SQL Server .I have gone through some books, but i have never seen the approach u have described. Where can I read more about the kind of stuff you are describing, OR does it just come from experience... |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2005-03-22 : 07:24:27
|
20 years experience I guess ....... and now you tell me I have to write a book?  Kristen |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-03-22 : 10:34:50
|
| We do something similar to what Kristen does with some twists and turns. :)We store all of our SQL objects in SourceSafe in a development tree.The developers check out code and develop on the development server.On completion, they check in the code and place the SourceSafe objects in a release folder.We have a tool that rolls the release folders to various environments.--QA for the QA team to test and signoff on.--UAT for the users to test and accept the risk/functionality. This is like Kristen's test environment.--RELEASE is for the developers and DBA team to test the release of the package against a copy of production.----Does the entire package run correctly.----Does it have any affects on the overall system.--PRODUCTION is the final roll.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2005-03-22 : 10:53:10
|
| It will probably depend on the size and nature of your situation as to how many "layers" you have in your setup. I would recommend that you never do anything directly onto the production environment. Things should be tested first in a dev environment that, if you're lucky, may be something similar to production.-------Moo. :) |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2005-03-22 : 15:53:21
|
| "Things should be tested first in a dev environment that, through years of experience, will be identical to production."Kristen |
|
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2005-03-23 : 04:24:20
|
quote:
Originally posted by Kristen
"Things should be tested first in a dev environment that, through years of experience, will be identical to production."
Sadly even the years of experience won't help if you have two different architectures.  -------Moo. :) |
|
|
|
|
|
|
|
|
General Question: Local Vs Live Server