General information
Forum:
Microsoft SQL Server
Title:
Clustered index on transactional tables?
Hi!
I have a huge problem with my database. When an user starts to use our system we provide the possibility to import his/her old databas contents to the new system. When I run the import script for this, it transfers large amount of data to the new databas (not unususal with 75000 rows/table).
The problem with this is that the import works fine but after it is finished my server/all my databases starts to act strange. I get different error messages, for example "connection broken" or "Server: Msg 3624, Level 20,". When I reboot my computer and run DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS things starts to work. (this is not the ideal thing to do because I might lose some of the data, but I didn't se any other ways)
I belive that it is one of my tables that is the problem, it is an transactional table i.e a table with lots of updates, inserts and deletes. But for prestanda reasons I have created a clustered compound index. I have now read that maybe clustered index is not a good idea on transactional tables. Is this true, and in that case is it because of the fragmentation?
Is it possible that this index causes to much fragmentation in this importscript and therefor screw up the entire sql server?
If not any suggestions of what is happening?
Would really appreciate some clarity in this (for me) confusing area!
Regards
Jenny
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only