Eric Fickes » bak http://ericfickes.com Independent Contractor for the internet : Adobe and Microsoft technologies Wed, 25 Aug 2010 16:53:25 +0000 en hourly 1 http://wordpress.org/?v=3.0.1 Store your SQL database in the same location as live http://ericfickes.com/2009/03/store-your-sql-database-in-the-same-location-as-live/ http://ericfickes.com/2009/03/store-your-sql-database-in-the-same-location-as-live/#comments Tue, 10 Mar 2009 06:25:25 +0000 Eric Fickes http://ericfickes.com/?p=520 I do a lot of moving of databases between development and production servers.  If I’m lucky, the production server I’m working with gives me access to DTS services, or even the Database publishing wizard.  More often than not however, the SQLServer I’m pushing to is locked down in a way that I am required to Remote Desktop into the server, then update the database via restore.

So here’s the tip.  When you’re only means of updating a remote SQLServer database is by physically restoring the database, do your best to mirror the product server’s database location on your development machine.  Check out this screenshot, and you’ll see what I mean

MSSQL : Restore Files and Filegroups

MSSQL : Restore Files and Filegroups

The background of this image shows that my production server houses all of it’s databases at the path C:\DB\database.mdf.

The lower right box shows where I keep my databases on my development server. Since I do not store any vital data on my C: drive, I’ve changed the path to D:\DB.

While this isn’t an exact path match, this trick saves me a little bit of time and frustration when restoring a database remotely.  Especially when I have to do it more than a handful of times in the same day.

It’s assumed you know how to the following  :

  • Back up a SQLServer database
  • Copy the BAK file to a remote server
  • Connect remotely to your SQLServer
  • Restore a Database file from a file ( BAK file )
]]> http://ericfickes.com/2009/03/store-your-sql-database-in-the-same-location-as-live/feed/ 0