Use Existing Server or Buy New Server? 1

[Mike555]

My small company has 22 computer users. We have a new server running Windows 2003 SBS (Premium Edition) and a Windows 2000 member server. I'll soon start the programming of a new SQL database, which all 22 of our users will utilize on a daily basis once it is completed. I'm trying to determine whether or not to run this database on the current 2003 SBS server, or to purchase a new server.

Currently, my SBS 2003 server runs Exchange 2003, ISA 2000, Anti-Virus, and shared folders/files. Among other things it contains Two 2.8gig Xeon processors, and 2GB DDR SDRAM 266mhz. Basically this server pretty much does it all, already. Would you think this server is suitable to handle the additional task of a SQL database with 22 concurrent users?

Ideally, I'd like to get a new server to run this database. But since my company is so small, we obviously would like to avoid the cost of a new server if possible.

What advice do you have? Thanks.

--
Mike

 

[RobertT687]

My $0.02 worth. I prefer a dedicated server, even one that isn't top-of-the-line exclusively for MSSQL. For the relatively small number of users you have, you may be able to get away with running it all on one machine. Keep in mind those other apps you mentioned all like to consume memory and CPU cycles. MSSQL works best when it is free to consume all the memory it thinks it needs. Question. If the Windows 2003 SBS is a 'new' server, what about running MSSQL on the 'old' server? What are the specs on the 'old' server?

 

[Mike555]

Thanks for your $0.02, RobertT687. Would you be able to give me an idea of the build that you would recommend for such a server, that isn't neccessarily the top-of-the-line and most expensive?

To answer your question about the 'old' server - The old server is a very old P3 - 512gig that cannot stay on for more than 10 minutes without crashing. The old server is not an option.

Thanks.

--
Mike

 

[RobertT687]

Again just my $0.02. I've always liked the Compaq Proliant line of servers. They have been used on several projects I've been involved with and have never given us any trouble. They are somewhat obsolecent these days and are widely available in the after-market. The Proliant 1600 and 1800 series are available as a tower or rack-mount unit.
Take a look at these sites:

http://www.focustechnology.com

http://www.pcsevolve.com/products/inventory_servers.asp

I found them on google with (used servers).

 

[Mike555]

RobertT687, I've never worked with MSDE before, but would this also be a viable option? Wouldn't MSDE allow me to distribute this application to up to 25 users?

--
Mike

 

[RobertT687]

MSDE has a couple of limitations that might effect its usefulness to you. First, the maximum size of the database it can handle is 2gig. Second, it doesn't come with a graphical manager like Enterprise Manager. Lastly (I could be wrong about this one) I think it's limited to 5 concurrent users. But you can hardly beat the price of $50.

 

[jgoodman00]

SQL Server is very resource hungry, & you will find that over time it will gradually consume all of the memory on your server. However, it is also capable of releasing memory back to the OS, should the OS require it. 22 users is not very many, so you might as well give it a shot. If it doesnt perform adequately then move it to a dedicated server.

You could also configure a maximum memory usage for SQL Server to stop it from doing this, & only allow it to use 1 of the processors. Depending on the usage SQL Server will be getting, this could be sufficient to keep things running smoothly...

James Goodman MCSE, MCDBA

http://www.angelfire.com/sports/f1pictures