Please help me determine what could cause the SQL Server 2000 Cluster error
listed below. This is a server with SQL Server 2000 Enterprise Edition as an
Active/Active Cluster and Windows 2003 Server.
Please help me with this error.
Thanks,
00000780.0000149c::2005/01/05-18:22:53.035 INFO [API] User denied access
using default cluster SD. GetLastError() = 0x00000005; dwStatus = 0x00000000.
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] printODBCError: sqlstate = 01000; native error = 2746;
message = [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite
(send()).
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = b;
message = [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network
error. Check your network documentation.
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] OnlineThread: QP is not online.
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Communication link failure
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Communication link failure
000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Communication link failure
000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Communication link failure
000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Communication link failure
00000780.00000e6c::2005/01/05-18:23:22.676 INFO [CP] CppRegNotifyThread
checkpointing key Software\Microsoft\Microsoft SQL Server\OLTP\MSSQLSERVER to
id 4 due to timer
00000780.00000e6c::2005/01/05-18:23:22.676 INFO [Qfs] QfsGetTempFileName
C:\Temp\, CLS, 41268 => C:\Temp\CLSA164.tmp, status 0
00000780.00000e6c::2005/01/05-18:23:22.676 INFO [Qfs] QfsDeleteFile
C:\Temp\CLSA164.tmp, status 0
00000780.00000e6c::2005/01/05-18:23:22.707 INFO [Qfs] QfsRegSaveKey
C:\Temp\CLSA164.tmp, status 0
The cluster is not running with the required access. Pls check the access by
giving the correct user / pass
Regards
Nirvan
"Joe P." wrote:
> Please help me determine what could cause the SQL Server 2000 Cluster error
> listed below. This is a server with SQL Server 2000 Enterprise Edition as an
> Active/Active Cluster and Windows 2003 Server.
> Please help me with this error.
> Thanks,
>
> 00000780.0000149c::2005/01/05-18:22:53.035 INFO [API] User denied access
> using default cluster SD. GetLastError() = 0x00000005; dwStatus = 0x00000000.
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] printODBCError: sqlstate = 01000; native error = 2746;
> message = [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite
> (send()).
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = b;
> message = [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network
> error. Check your network documentation.
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] OnlineThread: QP is not online.
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
> message = [Microsoft][ODBC SQL Server Driver]Communication link failure
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
> message = [Microsoft][ODBC SQL Server Driver]Communication link failure
> 000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
> 000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
> message = [Microsoft][ODBC SQL Server Driver]Communication link failure
> 000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
> 000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
> message = [Microsoft][ODBC SQL Server Driver]Communication link failure
> 000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
> 000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
> message = [Microsoft][ODBC SQL Server Driver]Communication link failure
> 00000780.00000e6c::2005/01/05-18:23:22.676 INFO [CP] CppRegNotifyThread
> checkpointing key Software\Microsoft\Microsoft SQL Server\OLTP\MSSQLSERVER to
> id 4 due to timer
> 00000780.00000e6c::2005/01/05-18:23:22.676 INFO [Qfs] QfsGetTempFileName
> C:\Temp\, CLS, 41268 => C:\Temp\CLSA164.tmp, status 0
> 00000780.00000e6c::2005/01/05-18:23:22.676 INFO [Qfs] QfsDeleteFile
> C:\Temp\CLSA164.tmp, status 0
> 00000780.00000e6c::2005/01/05-18:23:22.707 INFO [Qfs] QfsRegSaveKey
> C:\Temp\CLSA164.tmp, status 0
>
|||This might help explain...
http://support.microsoft.com/default...b;en-us;291255
jg
[quote]Originally posted by Joe P.
[b]Please help me determine what could cause the SQL Server 2000 Cluster error
listed below. This is a server with SQL Server 2000 Enterprise Edition as an
Active/Active Cluster and Windows 2003 Server.
Please help me with this error.
Thanks,|||The service account that MSCS is running under connects to the SQL
instance every 60 seconds by default (configurable in advanced tab of
the SQL Server resource in cluster administrator) and runs
select @.@.server
using its trusted connection. If it's capable of doing that then it's
happy that the SQL instance is alive. It also does a looks alive poll
every 5 seconds (by default) but I'm not sure what it does for a looks
alive poll (probably just a quick check of the status of the MSSQLServer
service on the owner node).
Basically, make sure the cluster service account has a trusted
connection to the SQL server. All it needs is to be a member of the
public role in the master DB (which every login has anyway) so just add
a trusted login for it if it doesn't already exist.
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Nirvan Biswas wrote:
[vbcol=seagreen]
>The cluster is not running with the required access. Pls check the access by
>giving the correct user / pass
>Regards
>Nirvan
>"Joe P." wrote:
>
Showing posts with label cluster. Show all posts
Showing posts with label cluster. Show all posts
Wednesday, March 7, 2012
Saturday, February 25, 2012
Checkpoint - Not running?
Hi folks.
I have a SQL cluster running 2000. My databases are set to simple
recovery. The recovery interval on the server is set to zero.
My logfiles are continually growing on the servers in the cluster -
including the one in tempdb. I do not have long-running transactions,
nor do I have large transactions occurring. The minute I manually do a
checkpoint, the logfiles drop to under 1MB in size. Note that the size
of the logfiles grow to over 70% of the total size allocated in the
file and do cause the logfiles to autogrow.
It was my understanding that a checkpoint will occur if the logfile
size is over 70% of the total allocated size of the file.
Checkpointing is definitely not occurring.
Can anyone offer some suggestions or insight as to why the checkpoint
process seems...Dead?
TIA,
Brian
SP4 Build 8.00.2171 has a fix to this. It sorted the problem for us.
Hot fix/build list
http://www.aspfaq.com/sql2000builds.asp
Paul
<lameduck1000@.hotmail.com> wrote in message
news:1159455084.684715.57620@.m73g2000cwd.googlegro ups.com...
> Hi folks.
> I have a SQL cluster running 2000. My databases are set to simple
> recovery. The recovery interval on the server is set to zero.
> My logfiles are continually growing on the servers in the cluster -
> including the one in tempdb. I do not have long-running transactions,
> nor do I have large transactions occurring. The minute I manually do a
> checkpoint, the logfiles drop to under 1MB in size. Note that the size
> of the logfiles grow to over 70% of the total size allocated in the
> file and do cause the logfiles to autogrow.
> It was my understanding that a checkpoint will occur if the logfile
> size is over 70% of the total allocated size of the file.
> Checkpointing is definitely not occurring.
> Can anyone offer some suggestions or insight as to why the checkpoint
> process seems...Dead?
> TIA,
> Brian
>
|||To verify whether or when a checkpoint is issued, you can turn on trace flag
3502 so that an entry is written to the errorlog when a checkpoint is issued.
Linchi
"lameduck1000@.hotmail.com" wrote:
> Hi folks.
> I have a SQL cluster running 2000. My databases are set to simple
> recovery. The recovery interval on the server is set to zero.
> My logfiles are continually growing on the servers in the cluster -
> including the one in tempdb. I do not have long-running transactions,
> nor do I have large transactions occurring. The minute I manually do a
> checkpoint, the logfiles drop to under 1MB in size. Note that the size
> of the logfiles grow to over 70% of the total size allocated in the
> file and do cause the logfiles to autogrow.
> It was my understanding that a checkpoint will occur if the logfile
> size is over 70% of the total allocated size of the file.
> Checkpointing is definitely not occurring.
> Can anyone offer some suggestions or insight as to why the checkpoint
> process seems...Dead?
> TIA,
> Brian
>
I have a SQL cluster running 2000. My databases are set to simple
recovery. The recovery interval on the server is set to zero.
My logfiles are continually growing on the servers in the cluster -
including the one in tempdb. I do not have long-running transactions,
nor do I have large transactions occurring. The minute I manually do a
checkpoint, the logfiles drop to under 1MB in size. Note that the size
of the logfiles grow to over 70% of the total size allocated in the
file and do cause the logfiles to autogrow.
It was my understanding that a checkpoint will occur if the logfile
size is over 70% of the total allocated size of the file.
Checkpointing is definitely not occurring.
Can anyone offer some suggestions or insight as to why the checkpoint
process seems...Dead?
TIA,
Brian
SP4 Build 8.00.2171 has a fix to this. It sorted the problem for us.
Hot fix/build list
http://www.aspfaq.com/sql2000builds.asp
Paul
<lameduck1000@.hotmail.com> wrote in message
news:1159455084.684715.57620@.m73g2000cwd.googlegro ups.com...
> Hi folks.
> I have a SQL cluster running 2000. My databases are set to simple
> recovery. The recovery interval on the server is set to zero.
> My logfiles are continually growing on the servers in the cluster -
> including the one in tempdb. I do not have long-running transactions,
> nor do I have large transactions occurring. The minute I manually do a
> checkpoint, the logfiles drop to under 1MB in size. Note that the size
> of the logfiles grow to over 70% of the total size allocated in the
> file and do cause the logfiles to autogrow.
> It was my understanding that a checkpoint will occur if the logfile
> size is over 70% of the total allocated size of the file.
> Checkpointing is definitely not occurring.
> Can anyone offer some suggestions or insight as to why the checkpoint
> process seems...Dead?
> TIA,
> Brian
>
|||To verify whether or when a checkpoint is issued, you can turn on trace flag
3502 so that an entry is written to the errorlog when a checkpoint is issued.
Linchi
"lameduck1000@.hotmail.com" wrote:
> Hi folks.
> I have a SQL cluster running 2000. My databases are set to simple
> recovery. The recovery interval on the server is set to zero.
> My logfiles are continually growing on the servers in the cluster -
> including the one in tempdb. I do not have long-running transactions,
> nor do I have large transactions occurring. The minute I manually do a
> checkpoint, the logfiles drop to under 1MB in size. Note that the size
> of the logfiles grow to over 70% of the total size allocated in the
> file and do cause the logfiles to autogrow.
> It was my understanding that a checkpoint will occur if the logfile
> size is over 70% of the total allocated size of the file.
> Checkpointing is definitely not occurring.
> Can anyone offer some suggestions or insight as to why the checkpoint
> process seems...Dead?
> TIA,
> Brian
>
Checkpoint - Not running?
Hi folks.
I have a SQL cluster running 2000. My databases are set to simple
recovery. The recovery interval on the server is set to zero.
My logfiles are continually growing on the servers in the cluster -
including the one in tempdb. I do not have long-running transactions,
nor do I have large transactions occurring. The minute I manually do a
checkpoint, the logfiles drop to under 1MB in size. Note that the size
of the logfiles grow to over 70% of the total size allocated in the
file and do cause the logfiles to autogrow.
It was my understanding that a checkpoint will occur if the logfile
size is over 70% of the total allocated size of the file.
Checkpointing is definitely not occurring.
Can anyone offer some suggestions or insight as to why the checkpoint
process seems...Dead?
TIA,
BrianSP4 Build 8.00.2171 has a fix to this. It sorted the problem for us.
Hot fix/build list
http://www.aspfaq.com/sql2000builds.asp
Paul
<lameduck1000@.hotmail.com> wrote in message
news:1159455084.684715.57620@.m73g2000cwd.googlegroups.com...
> Hi folks.
> I have a SQL cluster running 2000. My databases are set to simple
> recovery. The recovery interval on the server is set to zero.
> My logfiles are continually growing on the servers in the cluster -
> including the one in tempdb. I do not have long-running transactions,
> nor do I have large transactions occurring. The minute I manually do a
> checkpoint, the logfiles drop to under 1MB in size. Note that the size
> of the logfiles grow to over 70% of the total size allocated in the
> file and do cause the logfiles to autogrow.
> It was my understanding that a checkpoint will occur if the logfile
> size is over 70% of the total allocated size of the file.
> Checkpointing is definitely not occurring.
> Can anyone offer some suggestions or insight as to why the checkpoint
> process seems...Dead?
> TIA,
> Brian
>|||To verify whether or when a checkpoint is issued, you can turn on trace flag
3502 so that an entry is written to the errorlog when a checkpoint is issued
.
Linchi
"lameduck1000@.hotmail.com" wrote:
> Hi folks.
> I have a SQL cluster running 2000. My databases are set to simple
> recovery. The recovery interval on the server is set to zero.
> My logfiles are continually growing on the servers in the cluster -
> including the one in tempdb. I do not have long-running transactions,
> nor do I have large transactions occurring. The minute I manually do a
> checkpoint, the logfiles drop to under 1MB in size. Note that the size
> of the logfiles grow to over 70% of the total size allocated in the
> file and do cause the logfiles to autogrow.
> It was my understanding that a checkpoint will occur if the logfile
> size is over 70% of the total allocated size of the file.
> Checkpointing is definitely not occurring.
> Can anyone offer some suggestions or insight as to why the checkpoint
> process seems...Dead?
> TIA,
> Brian
>
I have a SQL cluster running 2000. My databases are set to simple
recovery. The recovery interval on the server is set to zero.
My logfiles are continually growing on the servers in the cluster -
including the one in tempdb. I do not have long-running transactions,
nor do I have large transactions occurring. The minute I manually do a
checkpoint, the logfiles drop to under 1MB in size. Note that the size
of the logfiles grow to over 70% of the total size allocated in the
file and do cause the logfiles to autogrow.
It was my understanding that a checkpoint will occur if the logfile
size is over 70% of the total allocated size of the file.
Checkpointing is definitely not occurring.
Can anyone offer some suggestions or insight as to why the checkpoint
process seems...Dead?
TIA,
BrianSP4 Build 8.00.2171 has a fix to this. It sorted the problem for us.
Hot fix/build list
http://www.aspfaq.com/sql2000builds.asp
Paul
<lameduck1000@.hotmail.com> wrote in message
news:1159455084.684715.57620@.m73g2000cwd.googlegroups.com...
> Hi folks.
> I have a SQL cluster running 2000. My databases are set to simple
> recovery. The recovery interval on the server is set to zero.
> My logfiles are continually growing on the servers in the cluster -
> including the one in tempdb. I do not have long-running transactions,
> nor do I have large transactions occurring. The minute I manually do a
> checkpoint, the logfiles drop to under 1MB in size. Note that the size
> of the logfiles grow to over 70% of the total size allocated in the
> file and do cause the logfiles to autogrow.
> It was my understanding that a checkpoint will occur if the logfile
> size is over 70% of the total allocated size of the file.
> Checkpointing is definitely not occurring.
> Can anyone offer some suggestions or insight as to why the checkpoint
> process seems...Dead?
> TIA,
> Brian
>|||To verify whether or when a checkpoint is issued, you can turn on trace flag
3502 so that an entry is written to the errorlog when a checkpoint is issued
.
Linchi
"lameduck1000@.hotmail.com" wrote:
> Hi folks.
> I have a SQL cluster running 2000. My databases are set to simple
> recovery. The recovery interval on the server is set to zero.
> My logfiles are continually growing on the servers in the cluster -
> including the one in tempdb. I do not have long-running transactions,
> nor do I have large transactions occurring. The minute I manually do a
> checkpoint, the logfiles drop to under 1MB in size. Note that the size
> of the logfiles grow to over 70% of the total size allocated in the
> file and do cause the logfiles to autogrow.
> It was my understanding that a checkpoint will occur if the logfile
> size is over 70% of the total allocated size of the file.
> Checkpointing is definitely not occurring.
> Can anyone offer some suggestions or insight as to why the checkpoint
> process seems...Dead?
> TIA,
> Brian
>
Checkpoint - Not running?
Hi folks.
I have a SQL cluster running 2000. My databases are set to simple
recovery. The recovery interval on the server is set to zero.
My logfiles are continually growing on the servers in the cluster -
including the one in tempdb. I do not have long-running transactions,
nor do I have large transactions occurring. The minute I manually do a
checkpoint, the logfiles drop to under 1MB in size. Note that the size
of the logfiles grow to over 70% of the total size allocated in the
file and do cause the logfiles to autogrow.
It was my understanding that a checkpoint will occur if the logfile
size is over 70% of the total allocated size of the file.
Checkpointing is definitely not occurring.
Can anyone offer some suggestions or insight as to why the checkpoint
process seems...Dead?
TIA,
BrianSP4 Build 8.00.2171 has a fix to this. It sorted the problem for us.
Hot fix/build list
http://www.aspfaq.com/sql2000builds.asp
Paul
<lameduck1000@.hotmail.com> wrote in message
news:1159455084.684715.57620@.m73g2000cwd.googlegroups.com...
> Hi folks.
> I have a SQL cluster running 2000. My databases are set to simple
> recovery. The recovery interval on the server is set to zero.
> My logfiles are continually growing on the servers in the cluster -
> including the one in tempdb. I do not have long-running transactions,
> nor do I have large transactions occurring. The minute I manually do a
> checkpoint, the logfiles drop to under 1MB in size. Note that the size
> of the logfiles grow to over 70% of the total size allocated in the
> file and do cause the logfiles to autogrow.
> It was my understanding that a checkpoint will occur if the logfile
> size is over 70% of the total allocated size of the file.
> Checkpointing is definitely not occurring.
> Can anyone offer some suggestions or insight as to why the checkpoint
> process seems...Dead?
> TIA,
> Brian
>|||To verify whether or when a checkpoint is issued, you can turn on trace flag
3502 so that an entry is written to the errorlog when a checkpoint is issued.
Linchi
"lameduck1000@.hotmail.com" wrote:
> Hi folks.
> I have a SQL cluster running 2000. My databases are set to simple
> recovery. The recovery interval on the server is set to zero.
> My logfiles are continually growing on the servers in the cluster -
> including the one in tempdb. I do not have long-running transactions,
> nor do I have large transactions occurring. The minute I manually do a
> checkpoint, the logfiles drop to under 1MB in size. Note that the size
> of the logfiles grow to over 70% of the total size allocated in the
> file and do cause the logfiles to autogrow.
> It was my understanding that a checkpoint will occur if the logfile
> size is over 70% of the total allocated size of the file.
> Checkpointing is definitely not occurring.
> Can anyone offer some suggestions or insight as to why the checkpoint
> process seems...Dead?
> TIA,
> Brian
>
I have a SQL cluster running 2000. My databases are set to simple
recovery. The recovery interval on the server is set to zero.
My logfiles are continually growing on the servers in the cluster -
including the one in tempdb. I do not have long-running transactions,
nor do I have large transactions occurring. The minute I manually do a
checkpoint, the logfiles drop to under 1MB in size. Note that the size
of the logfiles grow to over 70% of the total size allocated in the
file and do cause the logfiles to autogrow.
It was my understanding that a checkpoint will occur if the logfile
size is over 70% of the total allocated size of the file.
Checkpointing is definitely not occurring.
Can anyone offer some suggestions or insight as to why the checkpoint
process seems...Dead?
TIA,
BrianSP4 Build 8.00.2171 has a fix to this. It sorted the problem for us.
Hot fix/build list
http://www.aspfaq.com/sql2000builds.asp
Paul
<lameduck1000@.hotmail.com> wrote in message
news:1159455084.684715.57620@.m73g2000cwd.googlegroups.com...
> Hi folks.
> I have a SQL cluster running 2000. My databases are set to simple
> recovery. The recovery interval on the server is set to zero.
> My logfiles are continually growing on the servers in the cluster -
> including the one in tempdb. I do not have long-running transactions,
> nor do I have large transactions occurring. The minute I manually do a
> checkpoint, the logfiles drop to under 1MB in size. Note that the size
> of the logfiles grow to over 70% of the total size allocated in the
> file and do cause the logfiles to autogrow.
> It was my understanding that a checkpoint will occur if the logfile
> size is over 70% of the total allocated size of the file.
> Checkpointing is definitely not occurring.
> Can anyone offer some suggestions or insight as to why the checkpoint
> process seems...Dead?
> TIA,
> Brian
>|||To verify whether or when a checkpoint is issued, you can turn on trace flag
3502 so that an entry is written to the errorlog when a checkpoint is issued.
Linchi
"lameduck1000@.hotmail.com" wrote:
> Hi folks.
> I have a SQL cluster running 2000. My databases are set to simple
> recovery. The recovery interval on the server is set to zero.
> My logfiles are continually growing on the servers in the cluster -
> including the one in tempdb. I do not have long-running transactions,
> nor do I have large transactions occurring. The minute I manually do a
> checkpoint, the logfiles drop to under 1MB in size. Note that the size
> of the logfiles grow to over 70% of the total size allocated in the
> file and do cause the logfiles to autogrow.
> It was my understanding that a checkpoint will occur if the logfile
> size is over 70% of the total allocated size of the file.
> Checkpointing is definitely not occurring.
> Can anyone offer some suggestions or insight as to why the checkpoint
> process seems...Dead?
> TIA,
> Brian
>
Subscribe to:
Comments (Atom)