SQL Server or NOT!!!!!!!

[TheTomCat]

When do you recommend setting up SQL Sever? Do you base it the number of workstations?

I have some customers on a network with as many as ten (10) workstations and they work fine.

Also, I have NEVER done SQL Server. I have the SQL server 2000 that came with my Office XP Developer edition.
Do I load that on the customers server?



Thomas Bailey
a/k/a TomCat

http://www.reportcop.com

 

[SQLBill]

Don't load that on your customer's server. That is most likely the Developer Edition of SQL Server and is not licensed for production use.

What do you use your database for?
How much data do you expect to have in it (less than 2 GB or more than 2 GB)?

-SQLBill

Posting advice: FAQ481-4875

 

[TheTomCat]

It is a law enforcement forms database. It will have well less than 2gb. of data. A large database will be around 100 mb.

Do I load the SQL Server 2000 on my computer that I design the database on?

Thomas Bailey
a/k/a TomCat

http://www.reportcop.com

 

[Catadmin]

Tom,

You can load the Developer edition on the box that you are designing on with no problem. However, SQL Developer is never meant to go into production. Design away to your heart's content with the Dev version, then buy the real version for your client when you go to install SQL Server on their machines. If you decide to actually use SQL Server, you'll be installing the full version on the server and the client tools on the appropriate PCs.

Whether or not you use SQL Server is up to you really. There are other database products out there available from other companies. However, SQL Server is what I personally know, so I'll discuss it as opposed to Microsoft Access.

If you're going to have more than 4 people connected to this database at a time, then you definitely don't want to use MS Access. Access is a small tool designed for small companies. 2GB of database space isn't really that huge, but you can bet it's only going to grow from there. I've never seen a DB get smaller over time. Plus, with the number of potential connections, then yes, I advise you use SQL Server.

Aside from the # of simultaneous connections & potential db growth, my question is "Are they currently using any sort of database software to track their stuff?" Even a spreadsheet tool is a database (flat, though), so check to see if they're using Excel, Lotus, etc. for their work.

Lastly, you'll want to review with your client to see if there are any other processes or information keeping tasks they can potential move to the database. The more stuff you can take off their hands and stick into the database, the easier it is to justify moving to a tool like SQL Server. You'd be amazed at how many people without a database still keep hand-written records that they really don't have to keep that way.

Hope this helps.




Catadmin - MCDBA, MCSA
"The only stupid question is the one that *wasn't* asked.

 

[TheTomCat]

Thanks so much for your help catadmin.

Thomas Bailey
a/k/a TomCat

http://www.reportcop.com

 

[Catadmin]

You're welcome. I hope it helps you out.



Catadmin - MCDBA, MCSA
"The only stupid question is the one that *wasn't* asked.