Access Vs SQL Server 1

[fusionaire]

I am in the process of setting up an elaborate site that will need to input user data into five seperate databases, as well as query the information to be displayed later. I think in total, for each database I will have about 50 tables each, but most of those tables will be for reading information, not inserting. <br><br>So, my question is, has anyone encountered a similar obstacle before, and should I stick with Access or upgrade to SQL Server 7.0?<br><br>Thanks in advance

 

[jimmythegeek]

These are all questions you have to ask:<br><br>How many records will I be dealing with? Hundreds? Thousands? Millions?<br>Do I want Server side or Client side processing?<br>Is performance a huge issue?<br>Is cost an issue?<br>Am I familiar with SQL Server's T-SQL?<br>Which product do I know best?<br>Is development time an issue?<br><br><br>As far as records go, if you start getting over about 2 or 3 hundred thousand records, than you need to consider going to SQL Server.<br><br>Access can not do Server side processing while SQL Server can.<br><br>SQL Server is going to perform quite a bit faster than Access.<br><br>Access will be considerably cheaper. SQL Server will cost you around $1,100.00, plus as many licenses that you need.<br><br>If you are not familiar with T-SQL, then this will slow down your development time.<br><br>If development time is an issue, then you will have to consider any learning curve into it.<br><br>My opinion: (Take it for what it's worth)<br><br>I have worked with Access since version 1.1, and with SQL Server for almost 3 years. Both are wonderful products. But as far as performance goes, there is no comparison, SQL Server is a much better performer when it comes to speed of processing. If you are willing to take the time and learn it, then I think you will be more satisfied in the end, especially if you are working with a web site. You will have to use ADO with ASP pages to read and write data, but it is quick technology.<br><br>SQL Server 7.0 was a spectactular re-write from 6.5. It is much easier to use, and there is an interface similar to explorer, which makes things more familiar to the user. We converted a fairly large health care app from an Access back end to a SQL Server back-end, and the performance was like night and day. We unbound everything and used ADO, and that baby screamed.<br><br>Good luck on your decision. <br><br> <p>Jim Lunde<br><a href=mailto:compugeeks@hotmail.com>compugeeks@hotmail.com</a><br><a href=

http://www.cgeek.com>CompuGEEKS</a><br>Custom

Application Development

 

[fusionaire]

I will consider all of these factors over the weekend. Thank you very much for the advice.