|
Home > Archive > MS SQL Server > February 2006 > SQL Server 2005 Hanging
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SQL Server 2005 Hanging
|
|
| Amos Soma 2006-02-09, 9:23 am |
| We run a .NET (C#) application every night around 3:00 AM that creates a new
empty database and then executes roughly 3000-4000 SQL statements to create
the schema for this database (tables, stored procs, views etc.). Sometimes
this process works without error. Other times SQL Server 2005 hangs midway
through. Last night it hung again. I looked in our Event log and found the
following two entries:
"SQL Server Assertion: File: <latch.cpp>, line = 1535 Failed Assertion = '0'
Attempted release of unacquired latch. This error may be timing-related. If
the error persists after rerunning the statement, use DBCC CHECKDB to check
the database for structural integrity, or restart the server to ensure
in-memory data structures are not corrupted."
And
"A system assertion check has failed. Check the SQL Server error log for
details"
The SQL Log file doesn't contain much info except there is an entry that
says, "Description: Attempted Release of unacquired latch".
Then, after the two entries shown above, we get the following entries being
made (hundreds of them) almost continuously causing the server to hang. We
had to reboot.
"Time out occurred while waiting for buffer latch -- type 4, bp 032CFD84,
page 1:128, stat 0x3c0000b, database id: 2, allocation unit id:
281474980642816/3932160, task 0x008CCC58 : 0, waittime 13500, flags
0x200000a8, owning task 0x00000000. Continuing to wait."
One other comment. The first Event log entry shown above suggests we check
our database for structural integrity. I don't think that is an issue
because, as I stated in my first paragraph, we're creating a brand new
database and then executing SQL statements to create the schema.
Thanks for your help on this.
Amos.
| |
| John Bell 2006-02-09, 1:23 pm |
| Hi
The error looks a bit like
http://support.microsoft.com/defaul...kb;en-us;811052 do you have
autoshrink on?
Alternatively if the schema is constant, why not copy/attach a template
database that is already made?
John
"Amos Soma" wrote:
> We run a .NET (C#) application every night around 3:00 AM that creates a new
> empty database and then executes roughly 3000-4000 SQL statements to create
> the schema for this database (tables, stored procs, views etc.). Sometimes
> this process works without error. Other times SQL Server 2005 hangs midway
> through. Last night it hung again. I looked in our Event log and found the
> following two entries:
>
> "SQL Server Assertion: File: <latch.cpp>, line = 1535 Failed Assertion = '0'
> Attempted release of unacquired latch. This error may be timing-related. If
> the error persists after rerunning the statement, use DBCC CHECKDB to check
> the database for structural integrity, or restart the server to ensure
> in-memory data structures are not corrupted."
>
> And
>
> "A system assertion check has failed. Check the SQL Server error log for
> details"
>
> The SQL Log file doesn't contain much info except there is an entry that
> says, "Description: Attempted Release of unacquired latch".
>
> Then, after the two entries shown above, we get the following entries being
> made (hundreds of them) almost continuously causing the server to hang. We
> had to reboot.
>
> "Time out occurred while waiting for buffer latch -- type 4, bp 032CFD84,
> page 1:128, stat 0x3c0000b, database id: 2, allocation unit id:
> 281474980642816/3932160, task 0x008CCC58 : 0, waittime 13500, flags
> 0x200000a8, owning task 0x00000000. Continuing to wait."
>
> One other comment. The first Event log entry shown above suggests we check
> our database for structural integrity. I don't think that is an issue
> because, as I stated in my first paragraph, we're creating a brand new
> database and then executing SQL statements to create the schema.
>
> Thanks for your help on this.
>
> Amos.
>
>
>
| |
| Amos Soma 2006-02-09, 8:23 pm |
| John,
Autoshrink is off. And, the schema is not constant.
"John Bell" < jbellnewsposts@hotma
il.com> wrote in message
news:87685AA1-4F7A-434C-91DC- B61489854966@microso
ft.com...[color=darkred]
> Hi
>
> The error looks a bit like
> http://support.microsoft.com/defaul...kb;en-us;811052 do you have
> autoshrink on?
>
> Alternatively if the schema is constant, why not copy/attach a template
> database that is already made?
>
>
> John
>
> "Amos Soma" wrote:
>
| |
| John Bell 2006-02-10, 3:23 am |
| Hi
I can only suggest that you should try calling PSS then.
John
"Amos Soma" wrote:
> John,
>
> Autoshrink is off. And, the schema is not constant.
>
>
> "John Bell" < jbellnewsposts@hotma
il.com> wrote in message
> news:87685AA1-4F7A-434C-91DC- B61489854966@microso
ft.com...
>
>
>
|
|
|
|
|