ASP.NET Development SQL Server
Posted on 2011-09-06
What's a decent, simple way to reference a separate SQL server when developing, so that none of my testing hits the production server? I do all my own design, development and testing on my own. I already have a separate SQL server I can use.
I'm envisioning making a "clone" of all my databases on the soon-to-be development server, and then having to manually tweak connectionstrings in web.config every time I release. What's the proper way to do this?