Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Placing a Development Database on the same SQL Server instance as the Production database


Placing a Development Database on the same SQL Server instance as the Production database

Author
Message
George Hepworth
George Hepworth
SSC Veteran
SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)

Group: General Forum Members
Points: 264 Visits: 179
In discussions with a client, the option of placing a development copy of the database on the same server which will later be used for the production database. This is not the first choice, but does merit consideration as an option, I think. The reason for doing so would be to avoid the cost of a second license for SS on a development server.

However, before we consider that, we'd like to know what the potential dangers might be. One that was raised is that somehow a failure in the app using the development database could cause it to corrupt and, in turn, cause the server itself to crash, removing the server from service for the organization.

My questions are
A) how realistic is it to be afraid that a total corruption in one database (the dev version) would cause the loss of service in all other databases on that same server?

B) are there other reasons to avoid putting dev and production databases on the same server?

DOn't be afraid to tell me this is a bad idea if it is. I am just trying to consider all options on the table.

Thanks.

George
George Hepworth
George Hepworth
SSC Veteran
SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)

Group: General Forum Members
Points: 264 Visits: 179
I just thought of a second, more likely problem. An error in the development database could cause consumption of resources that would impact other databases. Also, there's the danger of the developer connecting to production instead of development and really hosing things up.

So, this does sound like a bad idea, but I'd still like to hear thoughts on the possibility of taking the whole server offline, as suggested, if something goes wrong in the development database.
Sean Lange
Sean Lange
SSCoach
SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)

Group: General Forum Members
Points: 16563 Visits: 17013
There are so many reasons this is a bad and so few reasons it is a good idea. Usually devs will have elevated privileges to the dev server that are not available to them in production. The resources being consumed on dev will have an impact on production, etc etc etc...

Get a copy of sql express installed somewhere else as your dev instance. Unless you need all the feature of enterprise on your dev system it should be adequate in most situations.

_______________________________________________________________

Need help? Help us help you.

Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

Need to split a string? Try Jeff Moden's splitter.

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs
Understanding and Using APPLY (Part 1)
Understanding and Using APPLY (Part 2)
Michael Valentine Jones
Michael Valentine Jones
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3254 Visits: 11771
SQL Server Developer Edition is only $50.00, so that SQL Server license cost is fairly small.
George Hepworth
George Hepworth
SSC Veteran
SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)

Group: General Forum Members
Points: 264 Visits: 179
The client told me that the Dev Edition was limited to a 180 evaluation period. Was he wrong about that?
Elliott Whitlow
Elliott Whitlow
SSCertifiable
SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)

Group: General Forum Members
Points: 6208 Visits: 5314
I'm gonna pile on.

This is a bad idea, there is so much that can go wrong that endangers your production environment that it simply isn't worth the risk.

You could build another instance perhaps but that would be very dependent on the amount of memory and processors, at least in this case you could better control your risks.

With all that said if they demand you do it I'd write up something specifying the dangers and make them sign off on it explicitly so later WHEN something happens they can't claim "we didn't know". Its not much but its something..

CEWII
George Hepworth
George Hepworth
SSC Veteran
SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)

Group: General Forum Members
Points: 264 Visits: 179
Forget I asked. :-D

I am looking into actual limitation of the Developers edition to verify the 180-day limitation objection.
Elliott Whitlow
Elliott Whitlow
SSCertifiable
SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)

Group: General Forum Members
Points: 6208 Visits: 5314
Dev edition is Enterprise Edition with a license that basically say you can't use it in production. It does not have a time limit. If you install a copy with an evaluation license it will expire. You pay for Developer Edition, its cheap like $50, you could install it as an eval and you would have 180 days but at that price point WHY?

CEWII
George Hepworth
George Hepworth
SSC Veteran
SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)

Group: General Forum Members
Points: 264 Visits: 179
The problem turns out to be finding the developer version for 2008 R2. Gee MS likes to be obscure.
Elliott Whitlow
Elliott Whitlow
SSCertifiable
SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)

Group: General Forum Members
Points: 6208 Visits: 5314
Google: purchase sql server 2012 developer edition

You should have at least 5 places to buy from. Keep in mind that you won't be able to buy SQL 2005 developer but you might be able to use the license for 2012 developer for 2005 developer.. I only point that out because of the fact you posted this in the SQL 2005 section.

CEWII
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search