Migrating tables to SQL server

pekajo

Registered User.
Local time
Today, 15:08
Joined
Jul 25, 2011
Messages
137
Hi,
I am starting to play around with migrating my tables to an SQL sever and have 3questions.
1. Can anyone point me to good information on the migration I can read or watch.
2. Does the FE use MS access to add/delete/edit the tables on the server or SQL. That is, if I have a form do I have to write SQL to add/delete/edit the tables on the server.
3. Is migrating to an sql server stable?
Thanks for any information.
Peter
 
Access can establish links to SQLServer tables. Form can use linked table as RecordSource. No need for SQL to enter/edit records but can do that if you want.

Stability and performance can be dependent on network. I have SQLServerExpress on my laptop and no issues.
 
Access can establish links to SQLServer tables. Form can use linked table as RecordSource. No need for SQL to enter/edit records but can do that if you want.

Stability and performance can be dependent on network. I have SQLServerExpress on my laptop and no issues.
Cheers
 
Hi,
I am starting to play around with migrating my tables to an SQL sever and have 3questions.
1. Can anyone point me to good information on the migration I can read or watch.
2. Does the FE use MS access to add/delete/edit the tables on the server or SQL. That is, if I have a form do I have to write SQL to add/delete/edit the tables on the server.
3. Is migrating to an sql server stable?
Thanks for any information.
Peter
1. Migrating data from Access to SQL Server has been around for decades and there is a ton of online documentation. A quick search using your favorite Search Engine should find many of them. I use Duck Duck Go, but you should be able to get results from Bing, Google, etc. as well.

2. Of course; that's the whole point of migrating Access data to SQL Server. You have to modify your Access FE to work effectively with the data in SQL Server. Many times people experience significant decreased performance after a migration. Your second online search should be for optimizing Access to work with SQL Server. Here's a link to YouTube playlist with a number of presentations on this topic.
3. Stability is one of the reasons for migrating from ACE to SQL Server. Of course, there are more factors to account for with SQL Server, but this is one of the strengths of that approach.
 
In my humble opinion, you should mentally approach this as follows:

1) First, I will become knowledgeable about (choosing/using) some of the more common SQL Server datatypes: (maybe Varchar, Nvarchar, Int, Decimal, Datetime - that pretty much covers almost everything I use)
2) Then and only then, I will begin studying the concept of switching from Access tables to SQL tables.

As tempting as it may be, it does not make sense to jump straight to #2.
That is like living on an island and considering moving to a new, relatively unknown (to you) island, and deeming Bridges the most important part of that study.

It is much better to get to the position where you independently know exactly how you are going to want your SQL tables.
Then worry about the relatively smaller issue of "how" to migrate them.

Just one man's opinion experience.
 
All reported - same spam on another user as well
 
@arnelgp Very naughty! Only kidding, definitely a hacked account. By the way, Last Pass password manager was hacked a while back. Not sure if you used it?
 
Yeah ... I think I heard my CISO talking about that and changing our GOTO passwords.
 

Users who are viewing this thread

Back
Top Bottom