![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We have a 64 bit SQL Server 2005 Cluster (Active/Passive) that was upgraded from a 32 bit SQL 2000 Server. Our cluster is not yet running Service Pack 2. We hosted an ASP.Net web application as the front end for a few internal contests. Over the course of these contests rarely and at intermittent intervals data duplications occurred. Here is an example showing what some of the data anomalies looked like: User Date Posted Question Answer user1 3/15/08 3:33 PM Communication involves the 4 following user1 3/15/08 3:33 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:33 PM What is the most important element user1 3/15/08 3:33 PM When it comes to heart disease, FALSE user1 3/15/08 3:34 PM Communication involves the 4 following user1 3/15/08 3:34 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:34 PM What is the most important element user1 3/15/08 3:34 PM When it comes to heart disease, FALSE Notice that the duplicate entries all happened 1 minute after the original insert. Could this behavior be caused by a miss configuration or problem with the SQL Server cluster? If so is upgrading to Service Pack 2 likely to resolve the issue or is there some other solution that is recommendable? |
#3
| |||
| |||
|
|
We have a 64 bit SQL Server 2005 Cluster (Active/Passive) that was upgraded from a 32 bit SQL 2000 Server. Our cluster is not yet running Service Pack 2. We hosted an ASP.Net web application as the front end for a few internal contests. Over the course of these contests rarely and at intermittent intervals data duplications occurred. Here is an example showing what some of the data anomalies looked like: User Date Posted Question Answer user1 3/15/08 3:33 PM Communication involves the 4 following user1 3/15/08 3:33 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:33 PM What is the most important element user1 3/15/08 3:33 PM When it comes to heart disease, FALSE user1 3/15/08 3:34 PM Communication involves the 4 following user1 3/15/08 3:34 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:34 PM What is the most important element user1 3/15/08 3:34 PM When it comes to heart disease, FALSE Notice that the duplicate entries all happened 1 minute after the original insert. Could this behavior be caused by a miss configuration or problem with the SQL Server cluster? If so is upgrading to Service Pack 2 likely to resolve the issue or is there some other solution that is recommendable? |
#4
| |||
| |||
|
|
We have a 64 bit SQL Server 2005 Cluster (Active/Passive) that was upgraded from a 32 bit SQL 2000 Server. Our cluster is not yet running Service Pack 2. We hosted an ASP.Net web application as the front end for a few internal contests. Over the course of these contests rarely and at intermittent intervals data duplications occurred. Here is an example showing what some of the data anomalies looked like: User Date Posted Question Answer user1 3/15/08 3:33 PM Communication involves the 4 following user1 3/15/08 3:33 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:33 PM What is the most important element user1 3/15/08 3:33 PM When it comes to heart disease, FALSE user1 3/15/08 3:34 PM Communication involves the 4 following user1 3/15/08 3:34 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:34 PM What is the most important element user1 3/15/08 3:34 PM When it comes to heart disease, FALSE Notice that the duplicate entries all happened 1 minute after the original insert. Could this behavior be caused by a miss configuration or problem with the SQL Server cluster? If so is upgrading to Service Pack 2 likely to resolve the issue or is there some other solution that is recommendable? |
#5
| |||
| |||
|
|
We have a 64 bit SQL Server 2005 Cluster (Active/Passive) that was upgraded from a 32 bit SQL 2000 Server. Our cluster is not yet running Service Pack 2. We hosted an ASP.Net web application as the front end for a few internal contests. Over the course of these contests rarely and at intermittent intervals data duplications occurred. Here is an example showing what some of the data anomalies looked like: User Date Posted Question Answer user1 3/15/08 3:33 PM Communication involves the 4 following user1 3/15/08 3:33 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:33 PM What is the most important element user1 3/15/08 3:33 PM When it comes to heart disease, FALSE user1 3/15/08 3:34 PM Communication involves the 4 following user1 3/15/08 3:34 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:34 PM What is the most important element user1 3/15/08 3:34 PM When it comes to heart disease, FALSE Notice that the duplicate entries all happened 1 minute after the original insert. Could this behavior be caused by a miss configuration or problem with the SQL Server cluster? If so is upgrading to Service Pack 2 likely to resolve the issue or is there some other solution that is recommendable? |
#6
| |||
| |||
|
|
We have a 64 bit SQL Server 2005 Cluster (Active/Passive) that was upgraded from a 32 bit SQL 2000 Server. Our cluster is not yet running Service Pack 2. We hosted an ASP.Net web application as the front end for a few internal contests. Over the course of these contests rarely and at intermittent intervals data duplications occurred. Here is an example showing what some of the data anomalies looked like: User Date Posted Question Answer user1 3/15/08 3:33 PM Communication involves the 4 following user1 3/15/08 3:33 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:33 PM What is the most important element user1 3/15/08 3:33 PM When it comes to heart disease, FALSE user1 3/15/08 3:34 PM Communication involves the 4 following user1 3/15/08 3:34 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:34 PM What is the most important element user1 3/15/08 3:34 PM When it comes to heart disease, FALSE Notice that the duplicate entries all happened 1 minute after the original insert. Could this behavior be caused by a miss configuration or problem with the SQL Server cluster? If so is upgrading to Service Pack 2 likely to resolve the issue or is there some other solution that is recommendable? |
#7
| |||
| |||
|
|
We have a 64 bit SQL Server 2005 Cluster (Active/Passive) that was upgraded from a 32 bit SQL 2000 Server. Our cluster is not yet running Service Pack 2. We hosted an ASP.Net web application as the front end for a few internal contests. Over the course of these contests rarely and at intermittent intervals data duplications occurred. Here is an example showing what some of the data anomalies looked like: User Date Posted Question Answer user1 3/15/08 3:33 PM Communication involves the 4 following user1 3/15/08 3:33 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:33 PM What is the most important element user1 3/15/08 3:33 PM When it comes to heart disease, FALSE user1 3/15/08 3:34 PM Communication involves the 4 following user1 3/15/08 3:34 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:34 PM What is the most important element user1 3/15/08 3:34 PM When it comes to heart disease, FALSE Notice that the duplicate entries all happened 1 minute after the original insert. Could this behavior be caused by a miss configuration or problem with the SQL Server cluster? If so is upgrading to Service Pack 2 likely to resolve the issue or is there some other solution that is recommendable? |
#8
| |||
| |||
|
|
We have a 64 bit SQL Server 2005 Cluster (Active/Passive) that was upgraded from a 32 bit SQL 2000 Server. Our cluster is not yet running Service Pack 2. We hosted an ASP.Net web application as the front end for a few internal contests. Over the course of these contests rarely and at intermittent intervals data duplications occurred. Here is an example showing what some of the data anomalies looked like: User Date Posted Question Answer user1 3/15/08 3:33 PM Communication involves the 4 following user1 3/15/08 3:33 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:33 PM What is the most important element user1 3/15/08 3:33 PM When it comes to heart disease, FALSE user1 3/15/08 3:34 PM Communication involves the 4 following user1 3/15/08 3:34 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:34 PM What is the most important element user1 3/15/08 3:34 PM When it comes to heart disease, FALSE Notice that the duplicate entries all happened 1 minute after the original insert. Could this behavior be caused by a miss configuration or problem with the SQL Server cluster? If so is upgrading to Service Pack 2 likely to resolve the issue or is there some other solution that is recommendable? |
#9
| |||
| |||
|
|
We have a 64 bit SQL Server 2005 Cluster (Active/Passive) that was upgraded from a 32 bit SQL 2000 Server. Our cluster is not yet running Service Pack 2. We hosted an ASP.Net web application as the front end for a few internal contests. Over the course of these contests rarely and at intermittent intervals data duplications occurred. Here is an example showing what some of the data anomalies looked like: User Date Posted Question Answer user1 3/15/08 3:33 PM Communication involves the 4 following user1 3/15/08 3:33 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:33 PM What is the most important element user1 3/15/08 3:33 PM When it comes to heart disease, FALSE user1 3/15/08 3:34 PM Communication involves the 4 following user1 3/15/08 3:34 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:34 PM What is the most important element user1 3/15/08 3:34 PM When it comes to heart disease, FALSE Notice that the duplicate entries all happened 1 minute after the original insert. Could this behavior be caused by a miss configuration or problem with the SQL Server cluster? If so is upgrading to Service Pack 2 likely to resolve the issue or is there some other solution that is recommendable? |
#10
| |||
| |||
|
|
We have a 64 bit SQL Server 2005 Cluster (Active/Passive) that was upgraded from a 32 bit SQL 2000 Server. Our cluster is not yet running Service Pack 2. We hosted an ASP.Net web application as the front end for a few internal contests. Over the course of these contests rarely and at intermittent intervals data duplications occurred. Here is an example showing what some of the data anomalies looked like: User Date Posted Question Answer user1 3/15/08 3:33 PM Communication involves the 4 following user1 3/15/08 3:33 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:33 PM What is the most important element user1 3/15/08 3:33 PM When it comes to heart disease, FALSE user1 3/15/08 3:34 PM Communication involves the 4 following user1 3/15/08 3:34 PM Cuál 2 ramas de la biblioteca ofrecen user1 3/15/08 3:34 PM What is the most important element user1 3/15/08 3:34 PM When it comes to heart disease, FALSE Notice that the duplicate entries all happened 1 minute after the original insert. Could this behavior be caused by a miss configuration or problem with the SQL Server cluster? If so is upgrading to Service Pack 2 likely to resolve the issue or is there some other solution that is recommendable? |
![]() |
| Thread Tools | |
| Display Modes | |
| |