| switching from Access to SQL |
| Jim Tanner posted at Tuesday, March 22, 2005 4:41 PM |
hey
i have an ASP app that has been functional for about 2 years now...... due to overwhelming traffic to the site (50,000 hits / day), we've noticed that our DB connection has been flaking out sometimes... (errors about file in use / unspecified errors when trying to cnonect)
so, we thought maybe switching the DB from Access to SQL Server may clear up this problem.
is SQL Server more tolerant of multiple concurrant connections? obviously, about 95% of the SQL syntax will be the same...... do you forsee any problems switchin from access to sql? |
 |
|
|
| |
| Access was never designed |
| Peter Bromberg replied at Tuesday, March 22, 2005 4:58 PM |
 | to handle a large number of concurrent connections. It is a file-based database.
Sql Server is a service, it is a broker-based database. Sql Server is designed to handle a large number of concurrent jobs efficiently.
You should not have any problems. You may have some work ahead writing stored procedures from your Access queries (the syntax can be somewhat different), but it will be good practice. |
 |
| |
| Datatype Conversion |
| Eddie Molieri replied at Tuesday, March 22, 2005 5:05 PM |
You should be aware of some datatype conversions. Not too much of a problem though. |
 |
| |
|
|