SQL Server 2000General discussion of Microsoft SQL Server -- for topics that don't fit in one of the more specific SQL Server forums. version 2000 only. There's a new forum for SQL Server 2005.
Welcome to the p2p.wrox.com Forums.
You are currently viewing the SQL Server 2000 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
I have SQL 2000 on a server which has 205gigs of space...
The database is 72gigs...
I created an intranet that access data from the DB...
I soon as I have a few people on it, it slows it down like crazy...
I created index keys on the fields being accessed...
Is there something I can do to make it faster...
It doesn't make any sence...
I don't think it's a database problem, I think its a bandwidth problem based on what you described. Get a fatter bandwidth internet connection. Database isn't web, it's not network bandwidth efficient....
You would think that the bandwidth would help...
Because i'm not really connecting to the internet...
I'm using the internet to browse to go get data from SQL Server...
But when you "go get data from the SQL server" all your data is going over a small bandwidth connection. Be careful you don't do "select * from X" because all the rows are then sent over your small bandwidth. Try exactly the same actions locally vs over the remote internet connected sql server and if you see a big big difference in speed, you know where your problem is. Generally it is a bad idea to connect to sql over the unsecured internet.
Slow Server when a few people accessing
