SQL Server express with Access environment
I've inherited an app that is written in Access 2007 (?) and has linked tables to SQL Server Express .
I'm used to using ODBC drivers to link to Oracle tables on a Windows server running Oracle, but not SQL Server.
I would like to mimic the environment on my desktop that the client has on theirs. I've copied the data using export and that should work, but for my own gratification, I would like to get up to speed on SQL Server Express. This might be the perfect opportunity.
What steps to I need to take to load SQL Server Express?
Is there a way I can export or backup the clients data and import it to my Access mdb?
What's the best way to accomplish this?
I'm used to using ODBC drivers to link to Oracle tables on a Windows server running Oracle, but not SQL Server.
I would like to mimic the environment on my desktop that the client has on theirs. I've copied the data using export and that should work, but for my own gratification, I would like to get up to speed on SQL Server Express. This might be the perfect opportunity.
What steps to I need to take to load SQL Server Express?
Is there a way I can export or backup the clients data and import it to my Access mdb?
What's the best way to accomplish this?
Who is Participating?
You need to download and install SQL Server 2008 Express including SQL Server Management Studion
Then restore your backup file using SSMS.
/gustav
Then restore your backup file using SSMS.
/gustav
Hi,
backups and detach/attach methods are good if you only want to copy a database in one direction. But if you also want to develop this database and then move your developments back to the production server you can't do this with backup or detach/attach because you would of course destroy the data which was added in the meantime.
So you should consider to install a deployment tool for this job which can also copy the production database to your machine (and this can also be done from an enterprise version to an express version or vice-versa).
Here's a good one which is free:
Atlantis Schema Inspector
and also:
Atlantis Data Inspector
Of course the better one is the Redgate SQL Toolbelt but also not very cheap.
Cheers,
Christian
backups and detach/attach methods are good if you only want to copy a database in one direction. But if you also want to develop this database and then move your developments back to the production server you can't do this with backup or detach/attach because you would of course destroy the data which was added in the meantime.
So you should consider to install a deployment tool for this job which can also copy the production database to your machine (and this can also be done from an enterprise version to an express version or vice-versa).
Here's a good one which is free:
Atlantis Schema Inspector
and also:
Atlantis Data Inspector
Of course the better one is the Redgate SQL Toolbelt but also not very cheap.
Cheers,
Christian
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
http://www.microsoft.com/en-us/download/details.aspx?id=29062
The link above is for 2012, but of course there are other versions. Be sure to use the one that is most relevant for you.
Once you do that, the easiest way to move a database is to Backup the database on the Source, and then Restore the database at your machine. You can do that with TSQL, or you can use SQL Server Management Studio. You can install SSMS from here:
http://www.microsoft.com/en-us/download/details.aspx?id=7593
One the source machine, you'd need to create a Backup database, which will create a single file (usually with the .bak extension). Grab that file, and move it over to your machine, and then Restore it to your local SSE install. This article has some further information on the Backup/Restore method:
http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/A_10138-How-to-upgrade-a-MSSQL-database-from-one-version-to-another.html
Once you do that, you'll have an exact copy of the database from your source.