No time for db maintenance

We are using the SQL 2000 server on a w2k server for collecting measuring
data, 24 hours a day, 365 days a year. The problem is that there is no time
for db maintenance when you have to put the database in single user mode.
The database is growing larger and larger and the response time is slower
and slower. How should I handle this ?
Normally it's no problem because most of our databases are just heavily
loaded at daytime and then you run the maintenance job at night. Must we
rewrite the application to use another database for some hours during
maintenace ?
Sincerely
\\Jonas BAt the very least, you should be defragging your indexes. This can be done
online with DBCC INDEXDEFRAG.
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Jonte@.bson.se" <jonasberthelsson@.hotmail.com> wrote in message
news:uOuENAiJEHA.620@.tk2msftngp13.phx.gbl...
We are using the SQL 2000 server on a w2k server for collecting measuring
data, 24 hours a day, 365 days a year. The problem is that there is no time
for db maintenance when you have to put the database in single user mode.
The database is growing larger and larger and the response time is slower
and slower. How should I handle this ?
Normally it's no problem because most of our databases are just heavily
loaded at daytime and then you run the maintenance job at night. Must we
rewrite the application to use another database for some hours during
maintenace ?
Sincerely
\\Jonas B|||There's no maintenance I can think of apart from running repairs that
requires putting the database into single-user mode. Checkout the whitepaper
http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx
which will give you advice on fragmentation related perf tuning.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:#p28uEiJEHA.1312@.TK2MSFTNGP12.phx.gbl...
> At the very least, you should be defragging your indexes. This can be
done
> online with DBCC INDEXDEFRAG.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com/sql
>
> "Jonte@.bson.se" <jonasberthelsson@.hotmail.com> wrote in message
> news:uOuENAiJEHA.620@.tk2msftngp13.phx.gbl...
> We are using the SQL 2000 server on a w2k server for collecting measuring
> data, 24 hours a day, 365 days a year. The problem is that there is no
time
> for db maintenance when you have to put the database in single user mode.
> The database is growing larger and larger and the response time is slower
> and slower. How should I handle this ?
> Normally it's no problem because most of our databases are just heavily
> loaded at daytime and then you run the maintenance job at night. Must we
> rewrite the application to use another database for some hours during
> maintenace ?
> Sincerely
> \\Jonas B
>