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
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
George Hepworth (6/21/2013)
The problem turns out to be finding the developer version for 2008 R2. Gee MS likes to be obscure.

It is not easy to find, but Google is your friend:

http://www.nextag.com/Microsoft-SQL-Server-2008-739594965/prices-html
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
Thanks for all the good advice.

I was able, finally, to get the client's IT to install SS 2008 R2 Express, but then I had to argue for two days to get him to uninstall the "Katmai" version of SSMS and replace it will SSMS 2008, which isn't perfect, but is functional.
EdVassie
EdVassie
Hall of Fame
Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)

Group: General Forum Members
Points: 3144 Visits: 3816
As others have said, running mixing non-Production and Production on the same server is a bad idea.

One of the main issues is Governance. It is established good practice to separate Production and non-Production to separate environments, so much so that any mixing of environments is seen as bad governance by almost everyone with the skills to work out what you have done or gets to hear about it. With the trivial per-instance cost today of running a separate virtualised non-Production environment, no-one can justify mixing non-Production and Production on the same server instance.

If your customers get to hear you are doing this, you will suffer reputational damage. Period. Potential customers will walk rather than sign with people that take governance this lightly. If you are under statutory regulation than do not expect the regulators to treat this lightly.

The next issue is stability and performance of your Production environment. This will suffer if you mix non-Production and Production on the same instance. If you ever get a Production outage that is caused by a non-Production system do not expect your senior management to treat this lightly. If this affects your stock market price do not expect yuor shareholders to treat this as competant management of their resources.

Part of choosing your own software vendors is to pick one who make either no or a nominal charge for non-Production environments. Vendors understand the need for good governance, and typically will prefer that you protect the Production environment rather than risk bad publicity because you can blame tham that your Production failure was mandated by their licensing policies. If you are talking with a vendor that insists on charging the same for non-Production as Production, this should be your turn to walk and find someone else.

You may want to look at http://sqlserverfinebuild.codeplex.com/wikipage?title=SQL%20Server%20Administration for more details.

Original author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005. 1 Dec 2016: now over 39,000 downloads.
Disclaimer: All information provided is a personal opinion that may not match reality.
Quote: "When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist." - Archbishop Hélder Câmara
Meet George Jetson
Meet George Jetson
SSCrazy
SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)

Group: General Forum Members
Points: 2635 Visits: 1393


I was able, finally, to get the client's IT to install SS 2008 R2 Express,


SQL Server 2008 R2 Express is NOT the same thing as SQL Server 2008 R2 Developer. It is with Express that your client will run into the 180 licensing limitation unless they purchase a fully licensed copy.

Chris Powell

George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
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
Yes, I know that SQL Express and SQL Developer edition are different. No, SQL Express is not time limited. The version I keep on my own Development machine has been around for a couple of years now.
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
Thanks, Ed. I appreciate the additional thoughts.
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
Meet George Jetson (6/25/2013)
It is with Express that your client will run into the 180 licensing limitation unless they purchase a fully licensed copy.

Express is not time limited, Evaluation is time limited. Express is free and you accept some limitations but one of those limitations is not time.

CEWII
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47204 Visits: 44367
Meet George Jetson (6/25/2013)


I was able, finally, to get the client's IT to install SS 2008 R2 Express,


SQL Server 2008 R2 Express is NOT the same thing as SQL Server 2008 R2 Developer. It is with Express that your client will run into the 180 licensing limitation unless they purchase a fully licensed copy.


Express is not time-limited. It's size-limited. Max 10GB per database, restricted to a single CPU core and 1GB of memory and with many, many unavailable features.
Personally I wouldn't consider developing on Express if production is Enterprise or over 10GB in size, too many things won't be available, it'll also be near-impossible to do sensible performance testing.


Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


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
GilaMonster (6/25/2013)
Express is not time-limited. It's size-limited. Max 10GB per database, restricted to a single CPU core and 1GB of memory and with many, many unavailable features.
Personally I wouldn't consider developing on Express if production is Enterprise or over 10GB in size, too many things won't be available, it'll also be near-impossible to do sensible performance testing.


+1

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