[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 314
  • Last Modified:

Upgrade Access to,SQL Server 2008 R2

I need to upgrade my access database to SQL SERVER. Can anyone tell me the process?
0
Idarac
Asked:
Idarac
1 Solution
 
Gregory MillerGeneral ManagerCommented:
First questions, do you have a SQL server? Why do you need to upgrade? Is this for a web application or desktop? How many simultaneous users will you have connecting? What version of MS Access?
0
 
Anthony PerkinsCommented:
The first thing you need to understand is that you are not "upgrading" when you go to SQL Server.  The data is being migrated to a totally different database that may or may not have all the functionality and performance you enjoyed with MS Access.

Having said that, yes you can just export your data from MS Access into SQL Server, however if you do that, you may find that the end result is not what you anticipated.  What I would do is analyze your database structure and see how it can or cannot be used in MS SQL Server, taking advantage of the strengths found in SQL Server and mitigating the functionality that is not there and you were used to when using MS Access.
0
 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
Give us some more details as to what you're trying to pull off here, and more importantly why.   If you can't provide us some details, we'll assume that this is a homework question and treat it accordingly.

As the above experts stated, an Access to SQL conversion is a big deal and not to be taken lightly.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
IdaracAuthor Commented:
OK fair enough this is not a homework question. Let me get some more details.
0
 
IdaracAuthor Commented:
Here is what I have. The client wants to get rid of Access as the database and replace it with an SQL Server database. The first phase will be replacing the the backend with SQL Server. The next phase will be replacing the Access frontend with a .Net app.
0
 
Anthony PerkinsCommented:
Actually the first phase is analyzing the database structure and code in MS Access to see how that translates to MS SQL Server.
0
 
IdaracAuthor Commented:
OK I have been through the database structure and looked at the fields I think they should be OK to go from Access to SQL Server. I have documented the code changes I will have to do but I know there will more that I missed.
0
 
Anthony PerkinsCommented:
Then I would start by creating the tables and views in SQL Server and migrate the data.  There are a number of tools that can help you with this process, but nothing compares to doing it manually.
0
 
IdaracAuthor Commented:
Once my app is ready for production I need to copy the data over all at once on a weekend or at night after hours

Do you know what tools so I can look for them?
0
 
Anthony PerkinsCommented:
I am confused.  if it is ready for Production that means that you have already developed and tested it using SQL Server.  If that is the case than I would use Red-Gates's SQL Server Compare and SQL Server Data Compare to migrate the schema and data from your Development or Test SQL Server database to your Production SQL Server database.
0
 
IdaracAuthor Commented:
OK that will be helpful.

Our access app will be active while we develop our new app. It is coded in C# and we will move the data from Access to the Production SQL database. We will probably have overnight to do the migration so I am wondering what is the fastest way to do it.

Have you used SSMA for creating SQL database?
0
 
Anthony PerkinsCommented:
It is coded in C# and we will move the data from Access to the Production SQL database. We will probably have overnight to do the migration
Again, I am trying to understand.  Are you saying that you are developing your app using C# against an MS Access database and then want to port it directly (overnight) to Production using a SQL Server database without first testing using a SQL Server database?  If that is true, to put it bluntly, you are in for a wild ride and if your job depends on it you may want to update your resume.
0
 
IdaracAuthor Commented:
Sorry about the confusion. But yes that would be a wild ride wouldn't it.
As we do our development yes we will be creating the new SQL Server database. The new app will be created against the new SQL Server database.
But while we are developing the new app and the new SQL Server database our existing app using the Access database will be in production.
So when development is complete we will have the new SQL Server database complete.

We will have
1. Our new SQL Server database
2. The existing production Access database

Now we have to move the Access data into our SQL Server database.
0
 
Anthony PerkinsCommented:
Then I go back to the recommendation I made earlier, namely:
I would use Red-Gates's SQL Server Compare and SQL Server Data Compare to migrate the schema and data from your Development or Test SQL Server database to your Production SQL Server database.
0
 
IdaracAuthor Commented:
Thank you
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now