Schaeffrcc
Technical User
I work for a company that runs 4 Databases on one SQL 7.0 server. We can not upgrade to SQL 2000 because on 2 of our applications, built in PowerBuilder, can not handle the upgrade and are in the process of being rebuild. The current problem we are having is in an attempt to get out Disaster Recovery Process implemented, we installed Replication of our SQL 7.0 server to another SQL 7.0 server and the Power Builder Applications could not handle the addition of the Date/Time stamp Replication put on all of the Tables. We believe we have backed out all of the Replications and removed the extra column from every table and now when some users connect to the database through the client and run a search (Select statement) against the database and two of the 5 table used in the select statement can become locked for updates until that person closed the application of there process is killed through Enterprise Manager.
It seems random who locks the database, and not everyone does it when they look up data in the database.
Has anyone seen similar type issues, we have not ruled conclusively that it is related to Replication but it seems to have started when this replication testing started.
Please help,
Thomas.
It seems random who locks the database, and not everyone does it when they look up data in the database.
Has anyone seen similar type issues, we have not ruled conclusively that it is related to Replication but it seems to have started when this replication testing started.
Please help,
Thomas.
