Kategorier 

Taggar 

T-SQL     Datawarehouse     temp table     bugs     Techdays     Säkerhet     connect     history     sp1     login error     rebuild     CTP1     Extended Event     SSAS     XP_cmdshell     performance     feedback     access denied     #am_get_querystats     SQL Denali     CMS     0xC0202009     Microsoft     page splits     reorganize index     parallelism     Cluster     data warehouse     BOL     central management server     CU1     CTE     2005     sql 2005     SQL Server 2012     sp_MSForEachDB     2008     SQL Server     SQL2008     SQL server codename Denali     2000     filter     SSIS     security     sql 2008     connection     Reports     Logins     AcquireConnection     improve     profile     function     sql browser     concatenation     resource governor     package load     undocumented procedures     0xC0010014     error     SSRS 2008     Business Intelligence     transactions     virtuell     SSRS     features     DECIMAL     HADR     Activity Monitor     dbmail     platsannons SQL utvecklare     clean up     CU3     Page life expectancy     2011     parameters     create index     HEAP     gratis verktyg     constraint     DTA

Senaste inläggen 

Mirroring related Error: 3624, Severity: 20, State: 1

Skrivet den 27 januari 2012 15:44 i Steinar Andersen, Level 300, SQL Server 2008R2, sv, en Recently, I had the pleasure of troubleshooting several Error 3624 on a SQL Server 2008 R2 instance. It seems to be related to bulk copying in data to a principal database in a mirroring setup. The principal never runs into trouble, but the mirror database generates an error when trying to replay the transactions. It tries to initiate a lock escalation, but fails for some unknown reason. The mirroring session is then suspended, and will have to be reinitialized from start. From this Microsoft Knowledgebase article http://support.microsoft.com/kb/974319 it seems that this problem should be fixed in CU1 for SQL Server 2008 R2. But we got the exact same problem even though we were running on SP1 (10.50.2500). So it seems that this error might have resurfaced, or that there exists a similar bug still. If you run into this problem, with SP1 installed, you should contact Microsoft Support. In the meantime, two workarounds should be possible. Either do a regular insert instead of an Bulk Insert, or you can break mirror beforehand and reinit it after the bulk insert operation. If you need help with SQL Server, we are always happy to help!

Kommentarer:


Skriv en kommentar

Ditt namn:
 
E-post:
 
Ämne:
Kommentar:
 

Due to problems with SPAM we have closed the possibility to comment. The function of commenting will be soon back!