Moving split database back end to sql server

[cbende2]

Hello all,



So the database I have right now is split, with the back end on our server.

Everything has been going great, however there are several second time delays when loading large forms, queries, etc.

I've heard that moving the back end to an sql server is the way to go for speed.

Does anyone have any experience with this?

Note: All forms and queries are on front end of database. Tables are located on the back end which is sitting on the server.

How would I go about doing this, I haven't done much research on it yet and just wanted to see what you guy's have experienced with this.

Thanks a bunch!

[rpeare]

The speed can be related to several things and moving to SQL, unless you already have SQL installed, may not be the solution due to expense.

If you are using bound forms and your tables have tons of data in them that is just a limitation of MS access, if you have tons of code running on a particular form that is slow that may be the issue as well and looking at optimizing code (creating modules etc) might provide some relief as well.

[cbende2]

SQL installed?

I don't have much code in my database, just large forms with several fields.

[rpeare]

SQL server is a Microsoft product. you can get a free version but I don't know it's limitations, a full version may cost hundreds to thousands of dollars. If you don't know if you have it installed you don't have it installed in all probability. Moving the back end to the server does not mean the back end is on SQL server. Moving the back end to the server would involve installing a version of MS SQL Server, duplicating the table structure of your MS Access database within SQL Server, then migrating all your data to the SQL tables, and finally re-linking the SQL Server tables into your Access database.

[cbende2]

So what is the point of changing from a split end database that has the back end on our server, to moving the back end onto an SQL server?

Edit:Sorry if that response sounded bitter or attacking, I'm just trying to have some questions answered

[Bob Fitz]

Hello all,

So the database I have right now is split, with the back end on our server.

Everything has been going great, however there are several second time delays when loading large forms, queries, etc.

I've heard that moving the back end to an sql server is the way to go for speed.

Does anyone have any experience with this?

Note: All forms and queries are on front end of database. Tables are located on the back end which is sitting on the server.

How would I go about doing this, I haven't done much research on it yet and just wanted to see what you guy's have experienced with this.

Thanks a bunch!

You may find the following link useful: http://www.granite.ab.ca/access/performancefaq.htm

[lfpm062010]

Hello all,

So the database I have right now is split, with the back end on our server.

Everything has been going great, however there are several second time delays when loading large forms, queries, etc.

I've heard that moving the back end to an sql server is the way to go for speed.

Does anyone have any experience with this?

Note: All forms and queries are on front end of database. Tables are located on the back end which is sitting on the server.

How would I go about doing this, I haven't done much research on it yet and just wanted to see what you guy's have experienced with this.

Thanks a bunch!

Maybe this article woudl explain the advantage and disadavantage.
http://www.expresstechnology.com/sup...er-over-access

For my own personal experience, I gained some and lost some. This is some of the Advantage and Disadvantage.

Advantage:
1) Security
2) No more 2 GB Limit with Access.
3) Speed is questionable. Depends on how you do it. Access Query Vs. Pass Thru Query.

Disadvantage:
1) Flexible on change structures.
2) Complexity on Query (mostly on Pass Thru Query).

[cbende2]

Thanks for the replies guys!