Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
rdemotsis
Starting Member
5 Posts |
Posted - 2001-06-06 : 11:58:50
|
| We recently moved our e-commerce site from a hosting service to in-house. The host was running SQL 7.0 sp2 on NT 4.0.We built a new environment in-house that was an Active-Passive Win2K cluster with SQL2k Clustered on a 4-way box. We stopped the web site and all activity on the SQL Server at the host site and made a backup of the database. The backup was restored to our new in-house system. The web site was switched over to our new in-house system and all seemed to go well. Later that afternoon we began experiencing time-outs between the web server and the SQL Server. The time-outs pointed to the MSDTC. We uninstalled the MSDTC and reinstalled it. We did not experience any time-outs for about 36 hours. We identified the tables that the time-outs were pointing to. We then dropped the foreign keys and rebuilt them. We have not had a time-out since. What could cause the Fkeys to become corrupt to the point where the MSDTC would cause time-outs? I am baffled |
|
|
|
|
|