March 7, 2003 at 12:46 pm
I have a table that is being transactionally replicated to another database. This table has a nonclusted PK contstraint and an additional 12 nonclustered indexes. Utilizing the sp_spaceused stored proc, I found out that the data size of this table is close to 1 GB. This might be causing some slowdowns with stored procs running of that table. Please advise.
March 7, 2003 at 1:29 pm
how wide is the table? can you post the schema? is the table used more on an OLAP or OLTP level?
March 7, 2003 at 1:34 pm
Your table is not that large as you image. As long as the table has beeb designed and indexed properly, you shouldn't see performance issues. If you have suspicion on stored procedures running slow, use Profiler to trace them and examine the execution plan to try to improve them.
How many rows the table has?
We have a table in size over 60 GB.
Edited by - Allen_Cui on 03/07/2003 1:42:44 PM
March 7, 2003 at 2:25 pm
Do you have a clustered index on this table?
Also can you post the DDL of the table and the index structures?
And finally why so many indexes?
March 7, 2003 at 2:41 pm
The other thing that might cause slow changes to the table is if you have foreign key defined on the table.
Also, if this is OLTP, why so many indexes?
Those could be also large and cause slow data manipulation.
Edited by - mromm on 03/07/2003 2:41:31 PM
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply