Link to home
Start Free TrialLog in
Avatar of Jim Horn
Jim HornFlag for United States of America

asked on

How to create backup of SQL Server db for purposes of creating it on a development pc

(Access Sage, SQL newbie)

Hello fellow experts

I have a client that has a SQL back-end, Access front-end where they want me to do some Access enhancements on it.  Is there a way to create a backup copy of their SQL back-end database for purposes of creating it on my development pc, for working on their front-end?

My alternative is to use a TightVNC-like connection to their server in order to do any work connected to the back-end, which I'd like to avoid if possible.

TIA
-Jim
ASKER CERTIFIED SOLUTION
Avatar of Kevin Hill
Kevin Hill
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jim Horn

ASKER

Good deal (funny man....)

Between the TightVNC connection and this, I'll try to demonstrate to this new, small client that I don't have all the time in the world to drive cross town to their offices and back, especially since I'm already committed 40 hrs/week to another client I'm happy with.

-Jim
understood....I do the same thing for one of mine.  But I use remote desktop, copy the existing, most recent backup file into a Zip file and send it to my FTP server.  From there I pull it to my workstation and restore it locally and reconnect the ADP to it
I was able to move the .bak file, but now I receive an error message:

Microsoft SQL-DMO (ODBC SQLState: 42000)
Device activation error.  The fhysical file name {old .mdf file location} ma be correct.  
How were attempting to restore?  Enterprise Manger or Query Analyzer....and did you change the physical file locations to something that exists on your local SQL Server?
Whoops nevermind.  I forgot to edit the 'Move to physical file name' path as you stated above.

I have the 'Restore Progress' dialog box now, and will PAQ when its complete.

Thanks.
-Jim
cool.  You may have to monkey around with dropping and adding users, depending on how you will be accessing the db.  Users generally get screwed up when moving databases to a different box.  Its the SID (SecurityID)
Worked like a charm.  Thanks.
NP...Jim...do you do ADPs?
Nope.  I haven't had a project yet that wasn't Access to a supported SQL Server, or anything just Access couldn't handle.
Darn....thanks anyway :-)