Hello,
I hope somebody can help in solving next problem.
Our SqlServer 2000 (installed on Win2003 EE) processes 15 millions of
records each day. It works fine about 7-8 days and then it starts to
slow down. Sometimes it seems that processing is stopped. There are
also periods where everything works fine. In windows EventViewer we
found an error regarding tempdb (could not allocate new page for
database 'tempdb'). We increased the size of tempdb log and data file
to 20GB, but it did not solved our problem.
No other errors appears in event viewer for sqlserver. All processing
are implemented with stored procedures using cursors and transactions.
Transactions are commited frequently. Recovery model is set to full.
Does anybody experienced similar problem so far?
J?j? - 12 Dec 2004 21:39 GMT
do you update your statistics and defrag your indexes?
wrong statistics = bad performance.
also examine your queries, if the tempdb is full, then you have a query
which fill it...
like a select ... group by
does your users can access the database at the same time you fill it through
your SP?
generally in a DW the recoevry model is set to simple or bulk-load because
the DW is generally a read-only database and logging bulk insert commands
will take a very big log.
have you try to use DTS to load your rows?
With a recovery model set to bulk-load, DTS will load your rows very quickly
and allow you to select the batch size.
> Hello,
>
[quoted text clipped - 11 lines]
>
> Does anybody experienced similar problem so far?