Server Service

Sunday, 17 February 2008

943656 Cumulative update package 5 for SQL Server 2005 Service Pack 2

Posted on 08:28 by Unknown

INTRODUCTION

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Cumulative Update 5 contains hotfixes for SQL Server 2005 issues that have been fixed since the release of Service Pack 2.

Note This build of the cumulative update package is also known as build 3215.

Posted in | No comments

Sunday, 21 October 2007

941450 Cumulative update package 4 for SQL Server 2005 Service Pack 2

Posted on 03:05 by Unknown

INTRODUCTION

Cumulative Update 4 contains hotfixes for SQL Server 2005 issues that have been fixed since the release of Service Pack 2.

Note This build of the cumulative update package is also known as build 3200.

Posted in | No comments

Friday, 12 January 2007

915307 FIX: You experience a slow uploading process if conflicts occur when many merge agents upload changes to the publishers at the same time in SQL

Posted on 13:18 by Unknown

http://support.microsoft.com/kb/915307/

SYMPTOMS

You have many merge agents in SQL Server 2005. For example, you have 500 merge agents. When these merge agents upload changes to the publishers at the same time, you experience a slow uploading process. In some cases, the uploading process never finishes.

This problem occurs if conflicts occur when these merge agents upload changes.

CAUSE

This problem occurs because the following behavior occurs when the merge agents try to log conflicts during the upload process:

When a merge agent queries the MSmerge_conflicts_info table, the query optimizer performs an Index Scan on the table instead of a Clustered Index Seek on the table.
No index is defined on the MSmerge_conflict_PublicationName_ArticleName table. When a merge agent queries the table, the query optimizer performs a Table Scan. When these merge agents log conflicts, SQL Server frequently queries the table. However, a Table Scan consumes lots of time if the table is big.

Additionally, a deadlock occurs in the following scenario:

One merge agent holds a lock on a user table at the publisher.
The merge agent requests a lock on the MSmerge_conflict_PublicationName_ArticleName table.
At the same time, another merge agent holds a lock on the MSmerge_conflict_PublicationName_ArticleName table and requests a lock on the same user table.

In this scenario, the merge agents block one another.

If a deadlock occurs, the uploading process never finishes.

Posted in | No comments

Thursday, 11 January 2007

927289 FIX: Updates to the SQL Server Mobile subscriber may not be reflected in the SQL Server 2005 merge publication

Posted on 12:21 by Unknown

SYMPTOMS

Consider the following scenario. A Microsoft SQL Server 2005 merge publication has a Microsoft SQL Server 2005 Mobile Edition (SQL Server Mobile) subscriber. In the merge publication, you create column filters on the articles of the publisher. In this scenario, updates to the SQL Server Mobile subscriber may not be reflected in the merge publication.

CAUSE

This problem occurs because the SQL Server Mobile subscriber does not track column version information for a vertically partitioned publication against a SQL Server subscriber.

Posted in | No comments

Wednesday, 10 January 2007

929179 FIX: A memory leak may occur every time that you synchronize a SQL Server Mobile subscriber in SQL Server 2005

Posted on 23:27 by Unknown

SYMPTOMS

Consider the following scenario. You create a merge publication in Microsoft SQL Server 2005. You configure Web synchronization for the merge publication. In this scenario, a memory leak may occur every time that you synchronize a Microsoft SQL Server 2005 Mobile Edition (SQL Server Mobile) subscriber. In the W3wp.exe process, the memory usage increases, and the number of handles increases.

CAUSE

This problem occurs because the Replrec.dll file leaks memory and leaks handles.

Posted in | No comments

Friday, 5 January 2007

Microsoft SQL Server Builds

Posted on 23:46 by Unknown

What version of SQL Server 2005 do I have?

This unofficial build chart lists all of the known KB articles, hotfixes and other builds of SQL Server 2005 that have been released.

Useful articles:

You can comment here. If you know of a hotfix build or KB that we don't have listed here, please use the comments.

Posted in | No comments

Server Service

Sunday, 17 February 2008

943656 Cumulative update package 5 for SQL Server 2005 Service Pack 2

Sunday, 21 October 2007

941450 Cumulative update package 4 for SQL Server 2005 Service Pack 2

Friday, 12 January 2007

915307 FIX: You experience a slow uploading process if conflicts occur when many merge agents upload changes to the publishers at the same time in SQL

SYMPTOMS

CAUSE

Thursday, 11 January 2007

927289 FIX: Updates to the SQL Server Mobile subscriber may not be reflected in the SQL Server 2005 merge publication

Wednesday, 10 January 2007

929179 FIX: A memory leak may occur every time that you synchronize a SQL Server Mobile subscriber in SQL Server 2005

Friday, 5 January 2007

Microsoft SQL Server Builds

Popular Posts

Blog Archive

About Me