Best Practices?

Hi,

I am installing SQL 2005 in a cluster env and there is a section which asks you about the domina\group for each of the accounts. I am going to have 3 virtual server so does it mean I should have 3*3 structure.

Can anyone tell me what exactly the group does and can there be 3 groups with 9 accounts.

What is the best practices
Thanks

I would just create one Windows Group with three different user accounts, then use one account for all of the services on each instance.

Best Practices?

Hi,

I am installing SQL 2005 in a cluster env and there is a section which asks you about the domina\group for each of the accounts. I am going to have 3 virtual server so does it mean I should have 3*3 structure.

Can anyone tell me what exactly the group does and can there be 3 groups with 9 accounts.

What is the best practices
Thanks

I would just create one Windows Group with three different user accounts, then use one account for all of the services on each instance.

Best practice for SQL cluster and domains

Hi All,
We have a critical 24x7 SQL cluster (W2K), which is a member of an NT 4
domain. As hardware is getting old, and NT4 domain is going to disappear in
the near future, the cluster has to be re-newed. There is also a trusted
Active Directory domain, which holds about all user accounts and groups.
These accounts and groups have been assigned appropriate rights to SQL and
application generated reports.
What makes this a bit more difficult, is that the company is also going to
split, as is network and AD. The split will take place within few months,
but the new AD (where the users finally will be located) is expected to be
in place and fully functional within one year. However, the new cluster
should be up and running within two months. The cluster will be built on
Windows server 2003 Enterprise.
What I should do, is to provide best scenario for implementing new cluster,
so that it minimizes work when AD domains in question change.
As far as I am concerned, if you change a cluster domain membership, you
need to rebuild the whole cluster. This is not what we want to do. We are
prepared to re-assign all appropriate user right and roles as users' domain
changes.
I see following scenarios:
1. join new cluster to present AD domain
2. install new cluster nodes as domain controllers for new "domainlet" or
domain and create trust relationships as needed
3. install separate domain controllers, and join cluster to this domain,
create trust relationships as needed
4. something else?
In scenario 1 I see most work; rebuilding the whole cluster within a year or
so. About scenarios 2 and 3 I'd like to have comments, especially about
using domainlets
(http://www.microsoft.com/windows2000...cluster/domain
lets.asp). Or, there might be a lot better option, which I have not come to
think about.
Please share your opinions and comments,
John
Great questions.
I like option 1, have you read http://support.microsoft.com/?id=319016, no
need to rebuild the cluster and start all over. Pretty easy actually.
Have you read http://support.microsoft.com/?id=298570, so option 2 is not
looking good.
Option 3 will work, but I hate extra trusts, if I can avoid them.
Go with number 1, that is what I would do
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"John" <someone@.microsoft.com> wrote in message
news:41f50ef2@.usenet01.boi.hp.com...
> Hi All,
> We have a critical 24x7 SQL cluster (W2K), which is a member of an NT 4
> domain. As hardware is getting old, and NT4 domain is going to disappear
> in
> the near future, the cluster has to be re-newed. There is also a trusted
> Active Directory domain, which holds about all user accounts and groups.
> These accounts and groups have been assigned appropriate rights to SQL and
> application generated reports.
> What makes this a bit more difficult, is that the company is also going to
> split, as is network and AD. The split will take place within few months,
> but the new AD (where the users finally will be located) is expected to be
> in place and fully functional within one year. However, the new cluster
> should be up and running within two months. The cluster will be built on
> Windows server 2003 Enterprise.
> What I should do, is to provide best scenario for implementing new
> cluster,
> so that it minimizes work when AD domains in question change.
> As far as I am concerned, if you change a cluster domain membership, you
> need to rebuild the whole cluster. This is not what we want to do. We are
> prepared to re-assign all appropriate user right and roles as users'
> domain
> changes.
> I see following scenarios:
> 1. join new cluster to present AD domain
> 2. install new cluster nodes as domain controllers for new "domainlet" or
> domain and create trust relationships as needed
> 3. install separate domain controllers, and join cluster to this domain,
> create trust relationships as needed
> 4. something else?
> In scenario 1 I see most work; rebuilding the whole cluster within a year
> or
> so. About scenarios 2 and 3 I'd like to have comments, especially about
> using domainlets
> (http://www.microsoft.com/windows2000...cluster/domain
> lets.asp). Or, there might be a lot better option, which I have not come
> to
> think about.
> Please share your opinions and comments,
> John
>
|||Rod,
thanks really, this was great information. I'll investigate the options
again in the light of your recent information, the scenario 1 looks now
actually quite good. If you have something to add, please do not hesitate to
share it
Cheers, John
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:%23z6TlkjAFHA.3592@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Great questions.
> I like option 1, have you read http://support.microsoft.com/?id=319016, no
> need to rebuild the cluster and start all over. Pretty easy actually.
> Have you read http://support.microsoft.com/?id=298570, so option 2 is not
> looking good.
> Option 3 will work, but I hate extra trusts, if I can avoid them.
> Go with number 1, that is what I would do
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://msmvps.com/clustering - Blog
> "John" <someone@.microsoft.com> wrote in message
> news:41f50ef2@.usenet01.boi.hp.com...
and[vbcol=seagreen]
to[vbcol=seagreen]
months,[vbcol=seagreen]
be[vbcol=seagreen]
are[vbcol=seagreen]
or[vbcol=seagreen]
year[vbcol=seagreen]
(http://www.microsoft.com/windows2000...cluster/domain
>

Best performance for SQL2000

Hi
i must configure a RAID on external storage disk array for my SQL 2000
cluster ad have think this configuration :
1- DataFile on separate RAID5 LUN
2- LogFile on another separate RAID5 LUN
3- Quorum on another separate RAID1 LUN
This configugation is good for performace (datafile e logfile separated) and
security (Quorum on Mirror) !'!
Thanks in advanceMake the Log on a RAID 1 or a 10 and not a 5. Raid 5 has too many writes
for peak performance of logs.Put the extra disks into the data raid 5 or
make it a raid 10 for better performance.
--
Andrew J. Kelly SQL MVP
<io.com> wrote in message news:OfbXh0YoEHA.1800@.TK2MSFTNGP15.phx.gbl...
> Hi
> i must configure a RAID on external storage disk array for my SQL 2000
> cluster ad have think this configuration :
> 1- DataFile on separate RAID5 LUN
> 2- LogFile on another separate RAID5 LUN
> 3- Quorum on another separate RAID1 LUN
> This configugation is good for performace (datafile e logfile separated)
and
> security (Quorum on Mirror) !'!
> Thanks in advance
>|||Ok therefore :
datafile RAID5
logfile RAID1
quorum RAID1
it's ok ?
thanks
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uFE6MNaoEHA.324@.TK2MSFTNGP11.phx.gbl...
> Make the Log on a RAID 1 or a 10 and not a 5. Raid 5 has too many writes
> for peak performance of logs.Put the extra disks into the data raid 5 or
> make it a raid 10 for better performance.
> --
> Andrew J. Kelly SQL MVP
>
> <io.com> wrote in message news:OfbXh0YoEHA.1800@.TK2MSFTNGP15.phx.gbl...
> > Hi
> >
> > i must configure a RAID on external storage disk array for my SQL 2000
> > cluster ad have think this configuration :
> >
> > 1- DataFile on separate RAID5 LUN
> > 2- LogFile on another separate RAID5 LUN
> > 3- Quorum on another separate RAID1 LUN
> >
> > This configugation is good for performace (datafile e logfile separated)
> and
> > security (Quorum on Mirror) !'!
> >
> > Thanks in advance
> >
> >
>|||Yes
--
Andrew J. Kelly SQL MVP
<io.com> wrote in message news:ORYQO1aoEHA.1608@.TK2MSFTNGP15.phx.gbl...
> Ok therefore :
> datafile RAID5
> logfile RAID1
> quorum RAID1
> it's ok ?
> thanks
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:uFE6MNaoEHA.324@.TK2MSFTNGP11.phx.gbl...
> > Make the Log on a RAID 1 or a 10 and not a 5. Raid 5 has too many
writes
> > for peak performance of logs.Put the extra disks into the data raid 5 or
> > make it a raid 10 for better performance.
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> >
> > <io.com> wrote in message news:OfbXh0YoEHA.1800@.TK2MSFTNGP15.phx.gbl...
> > > Hi
> > >
> > > i must configure a RAID on external storage disk array for my SQL 2000
> > > cluster ad have think this configuration :
> > >
> > > 1- DataFile on separate RAID5 LUN
> > > 2- LogFile on another separate RAID5 LUN
> > > 3- Quorum on another separate RAID1 LUN
> > >
> > > This configugation is good for performace (datafile e logfile
separated)
> > and
> > > security (Quorum on Mirror) !'!
> > >
> > > Thanks in advance
> > >
> > >
> >
> >
>|||Even better:
datafile RAID10
logfile RAID1
quorum RAID1
Regards
Mike
"io.com" wrote:
> Ok therefore :
> datafile RAID5
> logfile RAID1
> quorum RAID1
> it's ok ?
> thanks
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:uFE6MNaoEHA.324@.TK2MSFTNGP11.phx.gbl...
> > Make the Log on a RAID 1 or a 10 and not a 5. Raid 5 has too many writes
> > for peak performance of logs.Put the extra disks into the data raid 5 or
> > make it a raid 10 for better performance.
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> >
> > <io.com> wrote in message news:OfbXh0YoEHA.1800@.TK2MSFTNGP15.phx.gbl...
> > > Hi
> > >
> > > i must configure a RAID on external storage disk array for my SQL 2000
> > > cluster ad have think this configuration :
> > >
> > > 1- DataFile on separate RAID5 LUN
> > > 2- LogFile on another separate RAID5 LUN
> > > 3- Quorum on another separate RAID1 LUN
> > >
> > > This configugation is good for performace (datafile e logfile separated)
> > and
> > > security (Quorum on Mirror) !'!
> > >
> > > Thanks in advance
> > >
> > >
> >
> >
>
>

Best Configuration for a 3 Node SQL 2000 Cluster on Windows 2003?

Ok, I've got the cluster setup and running, but having never done this,
I'm not sure if I'm setting up SQL right... We're trying to migrate
our multitude of SQL Server running on older hardware to the new
cluster, but I want to make sure we don't shoot ourselves in the foot.
Here is what we've got:
Specs:
3 HP BL20P Blade Server (Twin 3.6GHz Xeon, 4GB Ram)
1 HP MSA1000 w/ Twin Fibre Switches (Dual Path Redundancy)
Current Setup:
Windows 2003 Enterprise, 20GB C:, 10GB D: (Pagefile), 37GB E: Data
MSA1000 is currently configured with 4 36GB Arrays (Quorum, 2 for Trans
Logs, and 1 for Backups) and 2 120GB Arrays (Database Data), but there
is about 1.2TB left on the controller for additional space.
Followed all the instructions, Public IPs, Private IPs, etc...
Installed SQL on the first two nodes (SQLCL01 & SQLCL02) and have two
Virtual Servers (Same name, actual server name is longer and unique),
and then two instances, INST1 on SQLCL01, and INST2 on SQLCL02.
SQLCL03 is the failover server which of course is identical to the
first two. We're never expecting to have 2 fail, but we may add a 4th
Server/Node in the future (we have 5 additional slots in our two Blade
Chassis).

>From what I've read you "can" install up to 16 instances into a single
cluster, but obviously I don't know if #1 I should try and install more
than 2 instances, or #2 if I even can. I've tried rerunning the SQL
Setup just to see, and all it lets me do it "modify" the current
install or remove it, it won't let me add another instance.
So... What am I looking at here? Is this the optimum configuration
for now, or can I do more? What about memory? Should I limit each SQL
Server instance to a certain level of RAM, say 3GB? Or possibly 2GB,
incase both the two main servers ever fail and everything gets forced
to the 3rd? These servers will pretty much only be used for SQL,
nothing else, so there isnt' too much worry about applications battling
for memory.
Thanks in advance. I know some of these questions may seem rather
newbish, but I've installed and administered SQL2k before, but never a
cluster... so this is new ground for me and the documentation out
there is not very helpful, most of it refers to SQL2k on Windows 2000,
not Windows Server 2003.
Jon Casimir
Lotsa comments inline.
<kazsmir@.gmail.com> wrote in message
news:1125515891.775160.31810@.z14g2000cwz.googlegro ups.com...
> Ok, I've got the cluster setup and running, but having never done this,
> I'm not sure if I'm setting up SQL right... We're trying to migrate
> our multitude of SQL Server running on older hardware to the new
> cluster, but I want to make sure we don't shoot ourselves in the foot.
> Here is what we've got:
> Specs:
> 3 HP BL20P Blade Server (Twin 3.6GHz Xeon, 4GB Ram)
> 1 HP MSA1000 w/ Twin Fibre Switches (Dual Path Redundancy)
> Current Setup:
> Windows 2003 Enterprise, 20GB C:, 10GB D: (Pagefile), 37GB E: Data
> MSA1000 is currently configured with 4 36GB Arrays (Quorum, 2 for Trans
> Logs, and 1 for Backups) and 2 120GB Arrays (Database Data), but there
> is about 1.2TB left on the controller for additional space.
>
I am not a big fan of blade servers as cluster nodes. Too many single
failure points for what is intended to be a highly available system.
A well-tuned, dedicated SQL server should have minimal need for a paging
file. If you are paging heavily, you have something tuned wrong.
Backups should never be stored on the same host computer or storage array as
the primary data store, even if they are on separate physical disks. Backup
across the net to a file share for immediate use and archive those files to
tape for longer retention periods.

> Followed all the instructions, Public IPs, Private IPs, etc...
> Installed SQL on the first two nodes (SQLCL01 & SQLCL02) and have two
> Virtual Servers (Same name, actual server name is longer and unique),
> and then two instances, INST1 on SQLCL01, and INST2 on SQLCL02.
> SQLCL03 is the failover server which of course is identical to the
> first two. We're never expecting to have 2 fail, but we may add a 4th
> Server/Node in the future (we have 5 additional slots in our two Blade
> Chassis).
This doesn't sound right. You should have each Virtual Server\Instance
combination installed on all nodes on the cluster so you can fail over as
needed. During install time you can select which cluster nodes to install
SQL to. You can set the preferred node order of each Virtual Server later
independently so they start and fail where you choose.
On a multi-node, multi-instance cluster, I usually only worry about
first-order failures. If I have more than one instance go south on me, it
is usually the entire cluster that bombs. If I have one instance with a
problem, somebody competent better be standing in front of it fixing the
problem within 30 minutes. You can adjust memory settings and failover
order at that time.

> cluster, but obviously I don't know if #1 I should try and install more
> than 2 instances, or #2 if I even can. I've tried rerunning the SQL
> Setup just to see, and all it lets me do it "modify" the current
> install or remove it, it won't let me add another instance.
>
SQL won't let you add a new virtual server unless there is at least one
unassigned cluster disk resource to anchor the instance. Whether you
"should" install more instances is another matter. Each instance looks and
acts like a separate server on the network. Generally, multiple instances
in a cluster are used to manage security and performance. In my history, I
find that one instance per node + one spare is an optimal configuration, but
your needs with this server consolidation project may vary.

> So... What am I looking at here? Is this the optimum configuration
> for now, or can I do more? What about memory? Should I limit each SQL
> Server instance to a certain level of RAM, say 3GB? Or possibly 2GB,
> incase both the two main servers ever fail and everything gets forced
> to the 3rd? These servers will pretty much only be used for SQL,
> nothing else, so there isnt' too much worry about applications battling
> for memory.
Since you have paid for Enterprise Edition anyway you should max out the
memory, although your choice of blade servers as hosts may limit that
expansion capability. You will need to consider what happens during a
failover so that you can tolerate "stacking" multiple instances on the same
nost node.

> Thanks in advance. I know some of these questions may seem rather
> newbish, but I've installed and administered SQL2k before, but never a
> cluster... so this is new ground for me and the documentation out
> there is not very helpful, most of it refers to SQL2k on Windows 2000,
> not Windows Server 2003.
Most of the considerations for Windows 2000 clustering apply to Windows
2003, except for some installation gotchas. Unless you are sure something
from Windows 2000 doesn't apply, assume it does.
Now is the best time to ask "dumb" questions. Later, when your "highly
available" database solution that you bet your job on is down is the worst
time.

> Jon Casimir
>
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP

BEGIN STACK DUMP error in log viewer

Hi

We are having problems with our application that uses SQL Server 2005 in a cluster environment. Sometimes the system stops answering and registers in the log viewer the following error:

=====================================================================

BugCheck Dump

=====================================================================

This file is generated by Microsoft SQL Server

version 9.00.1399.06

upon detection of fatal unexpected error. Please return this file, the query or program that produced the bugcheck, the database and the error log, and any other pertinent information with a Service Request.

Computer type is AT/AT COMPATIBLE.

Bios Version is IBM- 1001

Current time is 16:48:36 12/05/06.

2 Intel x86 level 15, 3600 Mhz processor (s).

Windows NT 5.2 Build 3790 CSD Service Pack 1.

Memory

MemoryLoad = 74%

Total Physical = 3327 MB

Available Physical = 858 MB

Total Page File = 9318 MB

Available Page File = 7058 MB

Total Virtual = 2047 MB

Available Virtual = 274 MB

**Dump thread - spid = 132, PSS = 0x71E09588, EC = 0x71E09590

***Stack Dump being sent to E:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0178.txt

* *******************************************************************************

*

* BEGIN STACK DUMP:

*12/05/06 16:48:36 spid 132

*

* Location:lckmgr.cpp:10820

* Expression:GetLocalLockPartition () == xactLockInfo->GetLocalLockPartition ()

* SPID:132

* Process ID:2436

*

* Input Buffer 255 bytes -

*?16 00 00 00 12 00 00 00 02 00 01 00 00 00 84 00 00 00

*???dD 01 00 00 00 ff ff 0a 00 02 00 00 00 e7 64 09 09 04 d0

*4dS E L E C T00 34 64 09 20 00 53 00 45 00 4c 00 45 00 43 00 54 00

*TAbleA (*) 20 00 54 00 48 00 69 00 73 00 74 00 6f 00 72 00 69 00

(*) There is a query here that I have excluded in the message

*

*MODULEBASEENDSIZE

* sqlservr0100000002BA7FFF01ba8000

* ntdll7C9100007C9D3FFF000c4000

* kernel327C8000007C90BFFF0010c000

* MSVCR8078130000781CAFFF0009b000

* msvcrt77B9000077BE9FFF0005a000

* MSVCP807C4200007C4A6FFF00087000

* ADVAPI3277D9000077E3DFFF000ae000

* RPCRT477C4000077CDEFFF0009f000

* USER3277F4000077FD1FFF00092000

* GDI3277BF000077C37FFF00048000

* CRYPT32760D000076164FFF00095000

* MSASN1760B0000760C1FFF00012000

* Secur3276E7000076E82FFF00013000

* MSWSOCK71970000719B1FFF00042000

* WS2_3271A5000071A66FFF00017000

* WS2HELP71A4000071A47FFF00008000

* USERENV7684000076904FFF000c5000

* opends60333E0000333E6FFF00007000

* NETAPI3271A9000071AE7FFF00058000

* SHELL327C9E00007D1EAFFF0080b000

* SHLWAPI77EE000077F31FFF00052000

* comctl327736000077462FFF00103000

* EntApi3700000037012FFF00013000

* PSAPI76A9000076A9AFFF0000b000

* WININET779D000077A78FFF000a9000

* OLEAUT3277CF000077D7BFFF0008c000

* ole327751000077643FFF00134000

* instapi4806000048069FFF 0000a000

* CLUSAPI74CF000074D01FFF00012000

* RESUTILS74E0000074E12FFF00013000

* sqlevn704F6100004F7A0FFF00191000

* SQLOS344D0000344D4FFF00005000

* rsaenh680000006802EFFF0002f000

* AUTHZ76B6000076B73FFF00014000

* MSCOREE340C000034104FFF00045000

* msv1_076BB000076BD6FFF00027000

* iphlpapi76C1000076C29FFF0001a000

* kerberos3433000034387FFF00058000

* cryptdll766000007660BFFF0000c000

* schannel7667000076696FFF00027000

* COMRES76F30000770BCFFF0018d000

* XOLEHLP343F0000343F5FFF00006000

* MSDTCPRX3440000034477FFF00078000

* msvcp60780C000078120FFF00061000

* MTXCLU74E5000074E68FFF00019000

* VERSION77B8000077B87FFF00008000

* WSOCK3271A0000071A09FFF0000a000

* DNSAPI76DF000076E1EFFF0002f000

* winrnr76E9000076E96FFF00007000

* WLDAP3276E3000076E5EFFF0002f000

* rasadhlp76EA000076EA7FFF00008000

* hnetcfg36190000361E8FFF00059000

* wshtcpip7193000071937FFF00008000

* security3634000036343FFF00004000

* msfte36A6000036CB7FFF00258000

* dbghelp36D0000036E17FFF00118000

* WINTRUST76AD000076AFAFFF 0002b000

* imagehlp76B3000076B58FFF00029000

* dssenh6810000068123FFF00024000

* NTMARTA777B0000777D1FFF00022000

* SAMLIB36FE000036FEEFFF0000f000

* ntdsapi7661000076624FFF00015000

* xpsp2res61BF000061EBFFFF002d0000

* CLBCatQ77650000776D2FFF00083000

* sqlncli61EC0000620E1FFF00222000

* COMCTL3277E4000077ED6FFF00097000

* comdlg32761D000076218FFF00049000

* SQLNCLIR007C0000007F2FFF00033000

* msftepxy621F000062204FFF00015000

* xpsqlbot6286000062865FFF00006000

* xpstar9062880000628C4FFF00045000

* SQLSCM90628E0000628E8FFF00009000

* ODBC32629000006293CFFF0003d000

* BatchParser90629400006295DFFF0001e000

* SQLSVC906297000062989FFF0001a000

* SqlResourceLoader629A0000629A5FFF00006000

* ATL807C6300007C64AFFF0001b000

* odbcint62B0000062B17FFF00018000

* SQLSVC9062B2000062B22FFF00003000

* xpstar9062B3000062B55FFF00026000

* xplog7062B6000062B6BFFF0000c000

* xplog7062B8000062B82FFF00003000

* oledb32631B000063228FFF00079000

* MSDART6323000063249FFF0001a000

* OLEDB32R634D0000634E1FFF00012000

* activeds76D1000076D42FFF 00033000

* adsldpc76CE000076D06FFF00027000

* credui76AA000076ACDFFF0002e000

* ATL769A0000769B7FFF00018000

* adsldp711100007113DFFF0002e000

* SXS75CB000075D6BFFF000bc000

* dbghelp65D4000065E52FFF00113000

*

*Edi: 6610BCB8:636A19003E3A604062F1A0406610D8AD0279E9003E3A63D8

*Esi: 00000000:

*Eax: 6610BB9C:000042AC00000000000000007C815E02000000007C931B34

*Ebx: 0000003F:

*Ecx: 6610C20C:00000000000100070000000000740072636A19046610BBCC

*Edx: 0000003D:

*Eip: 7C815E02:10C2C95E90909000A164909000000018C334408B891C428B

*Ebp: 6610BBEC:6610BC3002172CE4000042AC000000000000000000000000

*SegCs: 0000001B:

*EFlags: 00000246:

*Esp: 6610BB98:71E09588000042AC00000000000000007C815E0200000000

*SegSs: 78130023:000000000000000000000000000000000000000000000000

* *******************************************************************************

* -

* Short Stack Dump

7C815E02 Module(kernel32+00015E02)

02172CE4 Module(sqlservr+01172CE4)

02176BA0 Module(sqlservr+01176BA0)

02019506 Module(sqlservr+01019506)

015738EE Module(sqlservr+005738EE)

021B15B6 Module(sqlservr+011B15B6)

0163DD36 Module(sqlservr+0063DD36)

010E9FA3 Module(sqlservr+000E9FA3)

010B0F5F Module(sqlservr+000B0F5F)

0102C5F8 Module(sqlservr+0002C5F8)

01BEE12B Module(sqlservr+00BEE12B)

01BF2BCB Module(sqlservr+00BF2BCB)

01BF353D Module(sqlservr+00BF353D)

010438E5 Module(sqlservr+000438E5)

01041C35 Module(sqlservr+00041C35)

0100889F Module(sqlservr+0000889F)

010089C5 Module(sqlservr+000089C5)

010086E7 Module(sqlservr+000086E7)

010D764A Module(sqlservr+000D764A)

010D7B71 Module(sqlservr+000D7B71)

010D746E Module(sqlservr+000D746E)

010D83F0 Module(sqlservr+000D83F0)

781329AA Module(MSVCR80+000029AA)

78132A36 Module(MSVCR80+00002A36)

PSS @.0x71E09588

CSession @.0x71E08278

--

m_spid = 132m_cRef = 12m_rgcRefType[0] = 1

m_rgcRefType[1] = 1m_rgcRefType[2] = 9m_rgcRefType[3] = 1

m_rgcRefType[4] = 0m_rgcRefType[5] = 0m_pmo = 0x71E08040

m_pstackBhfPool = 0x00000000m_dwLoginFlags = 0x03e0m_fBackground = 0

m_fClientRequestConnReset = 0m_fUserProc = -1m_fConnReset = 0

m_fIsConnReset = 0m_fInLogin = 0m_fReplRelease = 0

m_fKill = 0m_ulLoginStamp = 3105683m_eclClient = 5

m_protType = 5m_hHttpToken = FFFFFFFF

m_pV7LoginRec

00000000:18010000 02000972 401f0000 00000006 400c0000 ?.......r@........@....

00000014:00000000 e0030000 00000000 00000000 5e000400 ?................^...

00000028:66000200 6a000000 7a001c00 b2000c00 ca000000 ?f...j...z...........

0000003C:ca001c00 02010000 02010b00 60f120db ad481801 ?............`. ..H..

00000050:00001801 00001801 00000000 0000???????????????..............

CPhysicalConnection @.0x71E08188

-

m_pPhyConn->m_pmo = 0x71E08040m_pPhyConn->m_pNetConn = 0x71E08788m_pPhyConn->m_pConnList = 0x71E08260

m_pPhyConn->m_pSess = 0x71E08278m_pPhyConn->m_fTracked = -1m_pPhyConn->m_cbPacketsize = 8000

m_pPhyConn->m_fMars = 0m_pPhyConn->m_fKill = 0

CBatch @.0x71E08A90

m_pSess = 0x71E08278m_pConn = 0x71E089F0m_cRef = 3

m_rgcRefType[0] = 1m_rgcRefType[1] = 1m_rgcRefType[2] = 1

m_rgcRefType[3] = 0m_rgcRefType[4] = 0m_pTask = 0x006F9D38

EXCEPT (null) @.0x6610B4AC

-

exc_number = 0exc_severity = 0exc_func = 0x023D96B0

Task @.0x006F9D38

-

CPU Ticks used (ms) = 1Task State = 2

WAITINFO_INTERNAL: WaitResource = 0x00000000WAITINFO_INTERNAL: WaitType = 0x0

WAITINFO_INTERNAL: WaitSpinlock = 0x00000000SchedulerId = 0x0

ThreadId = 0x444m_state = 0m_eAbortSev = 0

EC @.0x71E09590

--

spid = 132ecid = 0ec_stat = 0x0

ec_stat2 = 0x40ec_atomic = 0x4__fSubProc = 1

ec_dbccContext = 0x00000000__pSETLS = 0x71E08A30__pSEParams = 0x71E08CD0

__pDbLocks = 0x71E09878

SEInternalTLS @.0x71E08A30

-

m_flags = 0m_TLSstatus = 3m_owningTask = 0x006F9D38

m_activeHeapDatasetList = 0x71E08A30m_activeIndexDatasetList = 0x71E08A38

SEParams @.0x71E08CD0

--

m_lockTimeout = -1m_isoLevel = 1048576m_logDontReplicate = 0

m_neverReplicate = 0m_XactWorkspace = 0x03F78940m_pSessionLocks = 0x71E09A88

m_pDbLocks = 0x71E09878m_execStats = 0x3F867018m_pAllocFileLimit = 0x00000000

Does anybody know what’s going on?

I will be very appreciate if someone can help me to solve this problem. Thank you!

Hi,

We would like to investigate this issue. Can you please file a bug via http://connect.microsoft.com/sql. Please upload SqlDump0178.mdmp and SqlDump0178.txt there as well.

Thanks, Ron D.

|||any luck on this one. We are seeing the same error.

Thanks,
Siva|||

Make sure the table being accessed have proper CLUSTERED index.

BEGIN STACK DUMP error in log viewer

Hi

We are having problems with our application that uses SQL Server 2005 in a cluster environment. Sometimes the system stops answering and registers in the log viewer the following error:

=====================================================================

BugCheck Dump

=====================================================================

This file is generated by Microsoft SQL Server

version 9.00.1399.06

upon detection of fatal unexpected error. Please return this file, the query or program that produced the bugcheck, the database and the error log, and any other pertinent information with a Service Request.

Computer type is AT/AT COMPATIBLE.

Bios Version is IBM- 1001

Current time is 16:48:36 12/05/06.

2 Intel x86 level 15, 3600 Mhz processor (s).

Windows NT 5.2 Build 3790 CSD Service Pack 1.

Memory

MemoryLoad = 74%

Total Physical = 3327 MB

Available Physical = 858 MB

Total Page File = 9318 MB

Available Page File = 7058 MB

Total Virtual = 2047 MB

Available Virtual = 274 MB

**Dump thread - spid = 132, PSS = 0x71E09588, EC = 0x71E09590

***Stack Dump being sent to E:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0178.txt

* *******************************************************************************

*

* BEGIN STACK DUMP:

*12/05/06 16:48:36 spid 132

*

* Location:lckmgr.cpp:10820

* Expression:GetLocalLockPartition () == xactLockInfo->GetLocalLockPartition ()

* SPID:132

* Process ID:2436

*

* Input Buffer 255 bytes -

*?16 00 00 00 12 00 00 00 02 00 01 00 00 00 84 00 00 00

*???dD 01 00 00 00 ff ff 0a 00 02 00 00 00 e7 64 09 09 04 d0

*4dS E L E C T00 34 64 09 20 00 53 00 45 00 4c 00 45 00 43 00 54 00

*TAbleA (*) 20 00 54 00 48 00 69 00 73 00 74 00 6f 00 72 00 69 00

(*) There is a query here that I have excluded in the message

*

*MODULEBASEENDSIZE

* sqlservr0100000002BA7FFF01ba8000

* ntdll7C9100007C9D3FFF000c4000

* kernel327C8000007C90BFFF0010c000

* MSVCR8078130000781CAFFF0009b000

* msvcrt77B9000077BE9FFF0005a000

* MSVCP807C4200007C4A6FFF00087000

* ADVAPI3277D9000077E3DFFF000ae000

* RPCRT477C4000077CDEFFF0009f000

* USER3277F4000077FD1FFF00092000

* GDI3277BF000077C37FFF00048000

* CRYPT32760D000076164FFF00095000

* MSASN1760B0000760C1FFF00012000

* Secur3276E7000076E82FFF00013000

* MSWSOCK71970000719B1FFF00042000

* WS2_3271A5000071A66FFF00017000

* WS2HELP71A4000071A47FFF00008000

* USERENV7684000076904FFF000c5000

* opends60333E0000333E6FFF00007000

* NETAPI3271A9000071AE7FFF00058000

* SHELL327C9E00007D1EAFFF0080b000

* SHLWAPI77EE000077F31FFF00052000

* comctl327736000077462FFF00103000

* EntApi3700000037012FFF00013000

* PSAPI76A9000076A9AFFF0000b000

* WININET779D000077A78FFF000a9000

* OLEAUT3277CF000077D7BFFF0008c000

* ole327751000077643FFF00134000

* instapi4806000048069FFF 0000a000

* CLUSAPI74CF000074D01FFF00012000

* RESUTILS74E0000074E12FFF00013000

* sqlevn704F6100004F7A0FFF00191000

* SQLOS344D0000344D4FFF00005000

* rsaenh680000006802EFFF0002f000

* AUTHZ76B6000076B73FFF00014000

* MSCOREE340C000034104FFF00045000

* msv1_076BB000076BD6FFF00027000

* iphlpapi76C1000076C29FFF0001a000

* kerberos3433000034387FFF00058000

* cryptdll766000007660BFFF0000c000

* schannel7667000076696FFF00027000

* COMRES76F30000770BCFFF0018d000

* XOLEHLP343F0000343F5FFF00006000

* MSDTCPRX3440000034477FFF00078000

* msvcp60780C000078120FFF00061000

* MTXCLU74E5000074E68FFF00019000

* VERSION77B8000077B87FFF00008000

* WSOCK3271A0000071A09FFF0000a000

* DNSAPI76DF000076E1EFFF0002f000

* winrnr76E9000076E96FFF00007000

* WLDAP3276E3000076E5EFFF0002f000

* rasadhlp76EA000076EA7FFF00008000

* hnetcfg36190000361E8FFF00059000

* wshtcpip7193000071937FFF00008000

* security3634000036343FFF00004000

* msfte36A6000036CB7FFF00258000

* dbghelp36D0000036E17FFF00118000

* WINTRUST76AD000076AFAFFF 0002b000

* imagehlp76B3000076B58FFF00029000

* dssenh6810000068123FFF00024000

* NTMARTA777B0000777D1FFF00022000

* SAMLIB36FE000036FEEFFF0000f000

* ntdsapi7661000076624FFF00015000

* xpsp2res61BF000061EBFFFF002d0000

* CLBCatQ77650000776D2FFF00083000

* sqlncli61EC0000620E1FFF00222000

* COMCTL3277E4000077ED6FFF00097000

* comdlg32761D000076218FFF00049000

* SQLNCLIR007C0000007F2FFF00033000

* msftepxy621F000062204FFF00015000

* xpsqlbot6286000062865FFF00006000

* xpstar9062880000628C4FFF00045000

* SQLSCM90628E0000628E8FFF00009000

* ODBC32629000006293CFFF0003d000

* BatchParser90629400006295DFFF0001e000

* SQLSVC906297000062989FFF0001a000

* SqlResourceLoader629A0000629A5FFF00006000

* ATL807C6300007C64AFFF0001b000

* odbcint62B0000062B17FFF00018000

* SQLSVC9062B2000062B22FFF00003000

* xpstar9062B3000062B55FFF00026000

* xplog7062B6000062B6BFFF0000c000

* xplog7062B8000062B82FFF00003000

* oledb32631B000063228FFF00079000

* MSDART6323000063249FFF0001a000

* OLEDB32R634D0000634E1FFF00012000

* activeds76D1000076D42FFF 00033000

* adsldpc76CE000076D06FFF00027000

* credui76AA000076ACDFFF0002e000

* ATL769A0000769B7FFF00018000

* adsldp711100007113DFFF0002e000

* SXS75CB000075D6BFFF000bc000

* dbghelp65D4000065E52FFF00113000

*

*Edi: 6610BCB8:636A19003E3A604062F1A0406610D8AD0279E9003E3A63D8

*Esi: 00000000:

*Eax: 6610BB9C:000042AC00000000000000007C815E02000000007C931B34

*Ebx: 0000003F:

*Ecx: 6610C20C:00000000000100070000000000740072636A19046610BBCC

*Edx: 0000003D:

*Eip: 7C815E02:10C2C95E90909000A164909000000018C334408B891C428B

*Ebp: 6610BBEC:6610BC3002172CE4000042AC000000000000000000000000

*SegCs: 0000001B:

*EFlags: 00000246:

*Esp: 6610BB98:71E09588000042AC00000000000000007C815E0200000000

*SegSs: 78130023:000000000000000000000000000000000000000000000000

* *******************************************************************************

* -

* Short Stack Dump

7C815E02 Module(kernel32+00015E02)

02172CE4 Module(sqlservr+01172CE4)

02176BA0 Module(sqlservr+01176BA0)

02019506 Module(sqlservr+01019506)

015738EE Module(sqlservr+005738EE)

021B15B6 Module(sqlservr+011B15B6)

0163DD36 Module(sqlservr+0063DD36)

010E9FA3 Module(sqlservr+000E9FA3)

010B0F5F Module(sqlservr+000B0F5F)

0102C5F8 Module(sqlservr+0002C5F8)

01BEE12B Module(sqlservr+00BEE12B)

01BF2BCB Module(sqlservr+00BF2BCB)

01BF353D Module(sqlservr+00BF353D)

010438E5 Module(sqlservr+000438E5)

01041C35 Module(sqlservr+00041C35)

0100889F Module(sqlservr+0000889F)

010089C5 Module(sqlservr+000089C5)

010086E7 Module(sqlservr+000086E7)

010D764A Module(sqlservr+000D764A)

010D7B71 Module(sqlservr+000D7B71)

010D746E Module(sqlservr+000D746E)

010D83F0 Module(sqlservr+000D83F0)

781329AA Module(MSVCR80+000029AA)

78132A36 Module(MSVCR80+00002A36)

PSS @.0x71E09588

CSession @.0x71E08278

--

m_spid = 132m_cRef = 12m_rgcRefType[0] = 1

m_rgcRefType[1] = 1m_rgcRefType[2] = 9m_rgcRefType[3] = 1

m_rgcRefType[4] = 0m_rgcRefType[5] = 0m_pmo = 0x71E08040

m_pstackBhfPool = 0x00000000m_dwLoginFlags = 0x03e0m_fBackground = 0

m_fClientRequestConnReset = 0m_fUserProc = -1m_fConnReset = 0

m_fIsConnReset = 0m_fInLogin = 0m_fReplRelease = 0

m_fKill = 0m_ulLoginStamp = 3105683m_eclClient = 5

m_protType = 5m_hHttpToken = FFFFFFFF

m_pV7LoginRec

00000000:18010000 02000972 401f0000 00000006 400c0000 ?.......r@........@....

00000014:00000000 e0030000 00000000 00000000 5e000400 ?................^...

00000028:66000200 6a000000 7a001c00 b2000c00 ca000000 ?f...j...z...........

0000003C:ca001c00 02010000 02010b00 60f120db ad481801 ?............`. ..H..

00000050:00001801 00001801 00000000 0000???????????????..............

CPhysicalConnection @.0x71E08188

-

m_pPhyConn->m_pmo = 0x71E08040m_pPhyConn->m_pNetConn = 0x71E08788m_pPhyConn->m_pConnList = 0x71E08260

m_pPhyConn->m_pSess = 0x71E08278m_pPhyConn->m_fTracked = -1m_pPhyConn->m_cbPacketsize = 8000

m_pPhyConn->m_fMars = 0m_pPhyConn->m_fKill = 0

CBatch @.0x71E08A90

m_pSess = 0x71E08278m_pConn = 0x71E089F0m_cRef = 3

m_rgcRefType[0] = 1m_rgcRefType[1] = 1m_rgcRefType[2] = 1

m_rgcRefType[3] = 0m_rgcRefType[4] = 0m_pTask = 0x006F9D38

EXCEPT (null) @.0x6610B4AC

-

exc_number = 0exc_severity = 0exc_func = 0x023D96B0

Task @.0x006F9D38

-

CPU Ticks used (ms) = 1Task State = 2

WAITINFO_INTERNAL: WaitResource = 0x00000000WAITINFO_INTERNAL: WaitType = 0x0

WAITINFO_INTERNAL: WaitSpinlock = 0x00000000SchedulerId = 0x0

ThreadId = 0x444m_state = 0m_eAbortSev = 0

EC @.0x71E09590

--

spid = 132ecid = 0ec_stat = 0x0

ec_stat2 = 0x40ec_atomic = 0x4__fSubProc = 1

ec_dbccContext = 0x00000000__pSETLS = 0x71E08A30__pSEParams = 0x71E08CD0

__pDbLocks = 0x71E09878

SEInternalTLS @.0x71E08A30

-

m_flags = 0m_TLSstatus = 3m_owningTask = 0x006F9D38

m_activeHeapDatasetList = 0x71E08A30m_activeIndexDatasetList = 0x71E08A38

SEParams @.0x71E08CD0

--

m_lockTimeout = -1m_isoLevel = 1048576m_logDontReplicate = 0

m_neverReplicate = 0m_XactWorkspace = 0x03F78940m_pSessionLocks = 0x71E09A88

m_pDbLocks = 0x71E09878m_execStats = 0x3F867018m_pAllocFileLimit = 0x00000000

Does anybody know what’s going on?

I will be very appreciate if someone can help me to solve this problem. Thank you!

Hi,

We would like to investigate this issue. Can you please file a bug via http://connect.microsoft.com/sql. Please upload SqlDump0178.mdmp and SqlDump0178.txt there as well.

Thanks, Ron D.

|||any luck on this one. We are seeing the same error.

Thanks,
Siva|||

Make sure the table being accessed have proper CLUSTERED index.

BEGIN STACK DUMP error in log viewer

Hi

We are having problems with our application that uses SQL Server 2005 in a cluster environment. Sometimes the system stops answering and registers in the log viewer the following error:

=====================================================================

BugCheck Dump

=====================================================================

This file is generated by Microsoft SQL Server

version 9.00.1399.06

upon detection of fatal unexpected error. Please return this file, the query or program that produced the bugcheck, the database and the error log, and any other pertinent information with a Service Request.

Computer type is AT/AT COMPATIBLE.

Bios Version is IBM- 1001

Current time is 16:48:36 12/05/06.

2 Intel x86 level 15, 3600 Mhz processor (s).

Windows NT 5.2 Build 3790 CSD Service Pack 1.

Memory

MemoryLoad = 74%

Total Physical = 3327 MB

Available Physical = 858 MB

Total Page File = 9318 MB

Available Page File = 7058 MB

Total Virtual = 2047 MB

Available Virtual = 274 MB

**Dump thread - spid = 132, PSS = 0x71E09588, EC = 0x71E09590

***Stack Dump being sent to E:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0178.txt

* *******************************************************************************

*

* BEGIN STACK DUMP:

*12/05/06 16:48:36 spid 132

*

* Location:lckmgr.cpp:10820

* Expression:GetLocalLockPartition () == xactLockInfo->GetLocalLockPartition ()

* SPID:132

* Process ID:2436

*

* Input Buffer 255 bytes -

*?16 00 00 00 12 00 00 00 02 00 01 00 00 00 84 00 00 00

*???dD 01 00 00 00 ff ff 0a 00 02 00 00 00 e7 64 09 09 04 d0

*4dS E L E C T00 34 64 09 20 00 53 00 45 00 4c 00 45 00 43 00 54 00

*TAbleA (*) 20 00 54 00 48 00 69 00 73 00 74 00 6f 00 72 00 69 00

(*) There is a query here that I have excluded in the message

*

*MODULEBASEENDSIZE

* sqlservr0100000002BA7FFF01ba8000

* ntdll7C9100007C9D3FFF000c4000

* kernel327C8000007C90BFFF0010c000

* MSVCR8078130000781CAFFF0009b000

* msvcrt77B9000077BE9FFF0005a000

* MSVCP807C4200007C4A6FFF00087000

* ADVAPI3277D9000077E3DFFF000ae000

* RPCRT477C4000077CDEFFF0009f000

* USER3277F4000077FD1FFF00092000

* GDI3277BF000077C37FFF00048000

* CRYPT32760D000076164FFF00095000

* MSASN1760B0000760C1FFF00012000

* Secur3276E7000076E82FFF00013000

* MSWSOCK71970000719B1FFF00042000

* WS2_3271A5000071A66FFF00017000

* WS2HELP71A4000071A47FFF00008000

* USERENV7684000076904FFF000c5000

* opends60333E0000333E6FFF00007000

* NETAPI3271A9000071AE7FFF00058000

* SHELL327C9E00007D1EAFFF0080b000

* SHLWAPI77EE000077F31FFF00052000

* comctl327736000077462FFF00103000

* EntApi3700000037012FFF00013000

* PSAPI76A9000076A9AFFF0000b000

* WININET779D000077A78FFF000a9000

* OLEAUT3277CF000077D7BFFF0008c000

* ole327751000077643FFF00134000

* instapi4806000048069FFF 0000a000

* CLUSAPI74CF000074D01FFF00012000

* RESUTILS74E0000074E12FFF00013000

* sqlevn704F6100004F7A0FFF00191000

* SQLOS344D0000344D4FFF00005000

* rsaenh680000006802EFFF0002f000

* AUTHZ76B6000076B73FFF00014000

* MSCOREE340C000034104FFF00045000

* msv1_076BB000076BD6FFF00027000

* iphlpapi76C1000076C29FFF0001a000

* kerberos3433000034387FFF00058000

* cryptdll766000007660BFFF0000c000

* schannel7667000076696FFF00027000

* COMRES76F30000770BCFFF0018d000

* XOLEHLP343F0000343F5FFF00006000

* MSDTCPRX3440000034477FFF00078000

* msvcp60780C000078120FFF00061000

* MTXCLU74E5000074E68FFF00019000

* VERSION77B8000077B87FFF00008000

* WSOCK3271A0000071A09FFF0000a000

* DNSAPI76DF000076E1EFFF0002f000

* winrnr76E9000076E96FFF00007000

* WLDAP3276E3000076E5EFFF0002f000

* rasadhlp76EA000076EA7FFF00008000

* hnetcfg36190000361E8FFF00059000

* wshtcpip7193000071937FFF00008000

* security3634000036343FFF00004000

* msfte36A6000036CB7FFF00258000

* dbghelp36D0000036E17FFF00118000

* WINTRUST76AD000076AFAFFF 0002b000

* imagehlp76B3000076B58FFF00029000

* dssenh6810000068123FFF00024000

* NTMARTA777B0000777D1FFF00022000

* SAMLIB36FE000036FEEFFF0000f000

* ntdsapi7661000076624FFF00015000

* xpsp2res61BF000061EBFFFF002d0000

* CLBCatQ77650000776D2FFF00083000

* sqlncli61EC0000620E1FFF00222000

* COMCTL3277E4000077ED6FFF00097000

* comdlg32761D000076218FFF00049000

* SQLNCLIR007C0000007F2FFF00033000

* msftepxy621F000062204FFF00015000

* xpsqlbot6286000062865FFF00006000

* xpstar9062880000628C4FFF00045000

* SQLSCM90628E0000628E8FFF00009000

* ODBC32629000006293CFFF0003d000

* BatchParser90629400006295DFFF0001e000

* SQLSVC906297000062989FFF0001a000

* SqlResourceLoader629A0000629A5FFF00006000

* ATL807C6300007C64AFFF0001b000

* odbcint62B0000062B17FFF00018000

* SQLSVC9062B2000062B22FFF00003000

* xpstar9062B3000062B55FFF00026000

* xplog7062B6000062B6BFFF0000c000

* xplog7062B8000062B82FFF00003000

* oledb32631B000063228FFF00079000

* MSDART6323000063249FFF0001a000

* OLEDB32R634D0000634E1FFF00012000

* activeds76D1000076D42FFF 00033000

* adsldpc76CE000076D06FFF00027000

* credui76AA000076ACDFFF0002e000

* ATL769A0000769B7FFF00018000

* adsldp711100007113DFFF0002e000

* SXS75CB000075D6BFFF000bc000

* dbghelp65D4000065E52FFF00113000

*

*Edi: 6610BCB8:636A19003E3A604062F1A0406610D8AD0279E9003E3A63D8

*Esi: 00000000:

*Eax: 6610BB9C:000042AC00000000000000007C815E02000000007C931B34

*Ebx: 0000003F:

*Ecx: 6610C20C:00000000000100070000000000740072636A19046610BBCC

*Edx: 0000003D:

*Eip: 7C815E02:10C2C95E90909000A164909000000018C334408B891C428B

*Ebp: 6610BBEC:6610BC3002172CE4000042AC000000000000000000000000

*SegCs: 0000001B:

*EFlags: 00000246:

*Esp: 6610BB98:71E09588000042AC00000000000000007C815E0200000000

*SegSs: 78130023:000000000000000000000000000000000000000000000000

* *******************************************************************************

* -

* Short Stack Dump

7C815E02 Module(kernel32+00015E02)

02172CE4 Module(sqlservr+01172CE4)

02176BA0 Module(sqlservr+01176BA0)

02019506 Module(sqlservr+01019506)

015738EE Module(sqlservr+005738EE)

021B15B6 Module(sqlservr+011B15B6)

0163DD36 Module(sqlservr+0063DD36)

010E9FA3 Module(sqlservr+000E9FA3)

010B0F5F Module(sqlservr+000B0F5F)

0102C5F8 Module(sqlservr+0002C5F8)

01BEE12B Module(sqlservr+00BEE12B)

01BF2BCB Module(sqlservr+00BF2BCB)

01BF353D Module(sqlservr+00BF353D)

010438E5 Module(sqlservr+000438E5)

01041C35 Module(sqlservr+00041C35)

0100889F Module(sqlservr+0000889F)

010089C5 Module(sqlservr+000089C5)

010086E7 Module(sqlservr+000086E7)

010D764A Module(sqlservr+000D764A)

010D7B71 Module(sqlservr+000D7B71)

010D746E Module(sqlservr+000D746E)

010D83F0 Module(sqlservr+000D83F0)

781329AA Module(MSVCR80+000029AA)

78132A36 Module(MSVCR80+00002A36)

PSS @.0x71E09588

CSession @.0x71E08278

--

m_spid = 132m_cRef = 12m_rgcRefType[0] = 1

m_rgcRefType[1] = 1m_rgcRefType[2] = 9m_rgcRefType[3] = 1

m_rgcRefType[4] = 0m_rgcRefType[5] = 0m_pmo = 0x71E08040

m_pstackBhfPool = 0x00000000m_dwLoginFlags = 0x03e0m_fBackground = 0

m_fClientRequestConnReset = 0m_fUserProc = -1m_fConnReset = 0

m_fIsConnReset = 0m_fInLogin = 0m_fReplRelease = 0

m_fKill = 0m_ulLoginStamp = 3105683m_eclClient = 5

m_protType = 5m_hHttpToken = FFFFFFFF

m_pV7LoginRec

00000000:18010000 02000972 401f0000 00000006 400c0000 ?.......r@........@....

00000014:00000000 e0030000 00000000 00000000 5e000400 ?................^...

00000028:66000200 6a000000 7a001c00 b2000c00 ca000000 ?f...j...z...........

0000003C:ca001c00 02010000 02010b00 60f120db ad481801 ?............`. ..H..

00000050:00001801 00001801 00000000 0000???????????????..............

CPhysicalConnection @.0x71E08188

-

m_pPhyConn->m_pmo = 0x71E08040m_pPhyConn->m_pNetConn = 0x71E08788m_pPhyConn->m_pConnList = 0x71E08260

m_pPhyConn->m_pSess = 0x71E08278m_pPhyConn->m_fTracked = -1m_pPhyConn->m_cbPacketsize = 8000

m_pPhyConn->m_fMars = 0m_pPhyConn->m_fKill = 0

CBatch @.0x71E08A90

m_pSess = 0x71E08278m_pConn = 0x71E089F0m_cRef = 3

m_rgcRefType[0] = 1m_rgcRefType[1] = 1m_rgcRefType[2] = 1

m_rgcRefType[3] = 0m_rgcRefType[4] = 0m_pTask = 0x006F9D38

EXCEPT (null) @.0x6610B4AC

-

exc_number = 0exc_severity = 0exc_func = 0x023D96B0

Task @.0x006F9D38

-

CPU Ticks used (ms) = 1Task State = 2

WAITINFO_INTERNAL: WaitResource = 0x00000000WAITINFO_INTERNAL: WaitType = 0x0

WAITINFO_INTERNAL: WaitSpinlock = 0x00000000SchedulerId = 0x0

ThreadId = 0x444m_state = 0m_eAbortSev = 0

EC @.0x71E09590

--

spid = 132ecid = 0ec_stat = 0x0

ec_stat2 = 0x40ec_atomic = 0x4__fSubProc = 1

ec_dbccContext = 0x00000000__pSETLS = 0x71E08A30__pSEParams = 0x71E08CD0

__pDbLocks = 0x71E09878

SEInternalTLS @.0x71E08A30

-

m_flags = 0m_TLSstatus = 3m_owningTask = 0x006F9D38

m_activeHeapDatasetList = 0x71E08A30m_activeIndexDatasetList = 0x71E08A38

SEParams @.0x71E08CD0

--

m_lockTimeout = -1m_isoLevel = 1048576m_logDontReplicate = 0

m_neverReplicate = 0m_XactWorkspace = 0x03F78940m_pSessionLocks = 0x71E09A88

m_pDbLocks = 0x71E09878m_execStats = 0x3F867018m_pAllocFileLimit = 0x00000000

Does anybody know what’s going on?

I will be very appreciate if someone can help me to solve this problem. Thank you!

Hi,

We would like to investigate this issue. Can you please file a bug via http://connect.microsoft.com/sql. Please upload SqlDump0178.mdmp and SqlDump0178.txt there as well.

Thanks, Ron D.

|||any luck on this one. We are seeing the same error.

Thanks,
Siva

|||Make sure the table being accessed have proper CLUSTERED index.

BCV's on a cluster

Anyone out there using BCV with SQL 2000, ideally, or even SQL 2005? I've
got some questions and would like to speak with someone that's done it...
Many thanks, and Happy New Year!!
burt_king@.yahoo.com
"burt_king" <burt_king@.yahoo.com> wrote in message
news:AAF8DC41-78F4-4E67-A339-03F1A409B5D5@.microsoft.com...
> Anyone out there using BCV with SQL 2000, ideally, or even SQL 2005? I've
> got some questions and would like to speak with someone that's done it...
> Many thanks, and Happy New Year!!
> --
> burt_king@.yahoo.com
What are you trying to do? Many people use BCVs to then run their reporting
off of them or to run the backups off of them. Some people use BCVs as a
form of DR, too.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Denver starting Feb 12th
NYC starting Feb 19th
|||I'm not sure exactly what you meant by BCVs. But in the context of the EMC
SANs, BCV splits are commonly practiced and work fine. We often split BCVs on
our DR side, and check the BCV volumes to verify the databases on the DR side
and to test the procedures.
You can use BCVs for reporting. But in most of our cases, we need
near-real-time reports, and it's not practical to keep splitting and mounting
BCVs.
Linchi
"burt_king" wrote:

> Anyone out there using BCV with SQL 2000, ideally, or even SQL 2005? I've
> got some questions and would like to speak with someone that's done it...
> Many thanks, and Happy New Year!!
> --
> burt_king@.yahoo.com
>
|||To add to this, again in an EMC context.
BCV's are an exact copy of their sources, including the disk-signatrure
(sector 0)
Hence it is not recommended to present a split BCV to the cluster nodes, as
the signature is the same as the source disk which is under cluster control.
Presenting BCV's to another host outside the cluster ! ... no problem
HTH,
_Edwin.
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:7879E5CE-3247-4B65-BBD7-EE2620E5F9E9@.microsoft.com...
> I'm not sure exactly what you meant by BCVs. But in the context of the EMC
> SANs, BCV splits are commonly practiced and work fine. We often split BCVs
on
> our DR side, and check the BCV volumes to verify the databases on the DR
side
> and to test the procedures.
> You can use BCVs for reporting. But in most of our cases, we need
> near-real-time reports, and it's not practical to keep splitting and
mounting[vbcol=seagreen]
> BCVs.
> Linchi
> "burt_king" wrote:
I've[vbcol=seagreen]
it...[vbcol=seagreen]
|||Greetings, yes all, I'm speaking of EMC BCV's. We'd like to use them as we
do our Oracle databases but I don't think it's possible. With Oracle we put
tablespaces in hot backup mode, split off the BCV, run backups , control
files, force archive log switches and then for a database restore we can
restore the files and then apply logs.
My understanding of MSFT BCV use is that it's limited to quiescing the files
and then backing the files up. In a restore, for example, you'd restore the
BCV back and that's it. You cannot apply transaction logs.
Thoughts anyone? Whitepapers would be good too...
burt_king@.yahoo.com
"Russ Kaufmann [MVP]" wrote:

> "burt_king" <burt_king@.yahoo.com> wrote in message
> news:AAF8DC41-78F4-4E67-A339-03F1A409B5D5@.microsoft.com...
> What are you trying to do? Many people use BCVs to then run their reporting
> off of them or to run the backups off of them. Some people use BCVs as a
> form of DR, too.
>
> --
> Russ Kaufmann
> MVP - Windows Server - Clustering
> ClusterHelp.com, a Microsoft Certified Gold Partner
> Web http://www.clusterhelp.com
> Blog http://msmvps.com/clusterhelp
> The next ClusterHelp classes are:
> Denver starting Feb 12th
> NYC starting Feb 19th
>
>
|||"burt_king" <burt_king@.yahoo.com> wrote in message
news:F2EAAB01-0AD2-4A44-8A6E-A61D0793EF94@.microsoft.com...
> Greetings, yes all, I'm speaking of EMC BCV's.
A BCV is a BCV.

> We'd like to use them as we
> do our Oracle databases but I don't think it's possible. With Oracle we
> put
> tablespaces in hot backup mode, split off the BCV, run backups , control
> files, force archive log switches and then for a database restore we can
> restore the files and then apply logs.
You can do the same in the Microsoft world.

> My understanding of MSFT BCV use is that it's limited to quiescing the
> files
> and then backing the files up.
A BCV is a BCV, unless I am totally out in left field. It is created by the
SAN, not the OS.

> In a restore, for example, you'd restore the
> BCV back and that's it. You cannot apply transaction logs.
Why not? It is the same thing as a backed up database.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Denver starting Feb 12th
NYC starting Feb 19th
|||> > In a restore, for example, you'd restore the
> Why not? It is the same thing as a backed up database.
I have never used BCV as the starting point for a chain of log restores. Not
saying that it's not possible--I just don't know whether it's possible or
not. But since a BCV is split from the disk on which the database files
reside, it is in a state similar to that of the database files on the source
disk when the host is abruptly shut down. SQL Server can go through crash
recovery, when restarted, to bring the BCV into a transactionally consistent
state. But I'm not sure you can apply log backups to a BCV in that state.
For log restores, typically a database snapshot backup is taken, which does
require quiescing the database.
Again, I don't know whether some magic can be applied so that you can apply
log backups to a BCV. We have never done that, and I don't know anybody else
has done that.
Linchi
"Russ Kaufmann [MVP]" wrote:

> "burt_king" <burt_king@.yahoo.com> wrote in message
> news:F2EAAB01-0AD2-4A44-8A6E-A61D0793EF94@.microsoft.com...
> A BCV is a BCV.
>
> You can do the same in the Microsoft world.
>
> A BCV is a BCV, unless I am totally out in left field. It is created by the
> SAN, not the OS.
>
> Why not? It is the same thing as a backed up database.
>
> --
> Russ Kaufmann
> MVP - Windows Server - Clustering
> ClusterHelp.com, a Microsoft Certified Gold Partner
> Web http://www.clusterhelp.com
> Blog http://msmvps.com/clusterhelp
> The next ClusterHelp classes are:
> Denver starting Feb 12th
> NYC starting Feb 19th
>
>
|||To answer Russ' question, it cannot be used as part of a normal backup
strategy like Oracle because with oracle you run the alter tablespace backup
command which stops all writes to the file and all the action is kept in the
redo logs. In other words, it's just a file until the backup is done. With
SQL server, there's no such option. BCV's in the SQL Space involve running
the ioctrl (not sure I remember the correct name of the utility) which
quiesces all writes to the files, then split off the copy, then bring all the
files back on line.
In the event of a restore all the files are consistent to a point in time,
but you cannot apply logs to it. It is what it was at the moment of the snap.
burt_king@.yahoo.com
"Linchi Shea" wrote:
[vbcol=seagreen]
> I have never used BCV as the starting point for a chain of log restores. Not
> saying that it's not possible--I just don't know whether it's possible or
> not. But since a BCV is split from the disk on which the database files
> reside, it is in a state similar to that of the database files on the source
> disk when the host is abruptly shut down. SQL Server can go through crash
> recovery, when restarted, to bring the BCV into a transactionally consistent
> state. But I'm not sure you can apply log backups to a BCV in that state.
> For log restores, typically a database snapshot backup is taken, which does
> require quiescing the database.
> Again, I don't know whether some magic can be applied so that you can apply
> log backups to a BCV. We have never done that, and I don't know anybody else
> has done that.
> Linchi
> "Russ Kaufmann [MVP]" wrote:
|||"burt_king" <burt_king@.yahoo.com> wrote in message
news:AEF1E9C7-509C-4B92-B464-09AAD31D52D5@.microsoft.com...
> To answer Russ' question, it cannot be used as part of a normal backup
> strategy like Oracle because with oracle you run the alter tablespace
> backup
> command which stops all writes to the file and all the action is kept in
> the
> redo logs. In other words, it's just a file until the backup is done.
> With
> SQL server, there's no such option. BCV's in the SQL Space involve
> running
> the ioctrl (not sure I remember the correct name of the utility) which
> quiesces all writes to the files, then split off the copy, then bring all
> the
> files back on line.
> In the event of a restore all the files are consistent to a point in time,
> but you cannot apply logs to it. It is what it was at the moment of the
> snap.
If the BCV contains all files that existed on the source disk, then it is
the same thing as a flat file backup. As such, it can certainly be used as a
DR mechanism. You certainly could restore to that point in time. If you had
access to the other log files and check point files, then you should also be
able to do a restore and play back the log files. I see no reason that this
would not work.
However, I will also state that I am not a SQL expert.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Denver starting Feb 12th
NYC starting Feb 19th
|||Linchi,
If you are running EMC storage, please have a look at the Timefinder SQL
integration Module.
It can restore from BCV backup, mount the db, and all other tasks in order
to prepare for a log replay.
rgds,
Edwin.
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:5C661664-C828-4E14-B725-918A4D7A9EC1@.microsoft.com...
> Russ;
> Could you point me to any reference that indicates you can use a BCV as
the
> starting point to replay log backups? I don't think it would work. But
then[vbcol=seagreen]
> you never know.
> Linchi
> "Russ Kaufmann [MVP]" wrote:
in[vbcol=seagreen]
all[vbcol=seagreen]
time,[vbcol=seagreen]
the[vbcol=seagreen]
is[vbcol=seagreen]
as a[vbcol=seagreen]
had[vbcol=seagreen]
also be[vbcol=seagreen]
this[vbcol=seagreen]