Recently Rebuilt SQL2K Cluster

I have recently had to rebuild my SQL Server 2000 sp3a 2 node active/passive
cluster running on Windows 2000 AS SP4. We ran into issues about two weeks
ago after a SAN migration (I'll spare all the gory details). When my
previous cluster died, I used one of the nodes as a stand alone instance of
SQL Server (to run our production database). On the other former node, I
removed the OS clustering software and had to manually remove SQL Server. I
eventually (with the assistance of Donna L. at MS) was able to get a single
node cluster of SQL2K running on physical server PRODSQL01 (the virtual
server name is PRODSQLCL01). While the cluster was running as a single node
cluster, I applied sp3a and the 818 hotfix. I then migrated the data from
the stand alone instance to PRODSQLCL01 and started to use it for production.
I turned my attention to the other box and removed and reinstalled the
Windows 2000 cluster software. This box is now called PRODSQL02. I was able
to add PRODSQL02 to the windows cluster, and the successfully added it via
SQL Server setup to the virtual server. My issue now is that PRODSQL02 has
the RTM versions of the binaries. I am not sure if I have a setup issue or I
misunderstand point 3.10 of the sp3a readme. Currently the virtual server is
running on PRODSQL01. If I attempt follow the steps under "If you need to
rebuild a node in the failover cluster..." from PRODSQL02 I am only able to
select the Virtual Server, and if I continue setup I get this error "all
cluster disks available to this virtual server are owned by other node(s)"
and then "Setup was unable to verify the state of the server for an upgrade.
Verify the server is able to start and that you provided a valid sa password
and restart setup". I understand that the virtual resources are only
available on the currently active node, but the way I read the instructions I
should be able to run the service pack installation on the inactive node. Do
I need to rerun the SP (and hotfix) setup on SQL01 (since the virtual server
is running there)? Do I need to move the resources to SQL02 and run the SP
setup there? I just need clarification of where to run the SP setup since I
just added SQL02 to this cluster.
You should be able to run setup on the non-host node and it will upgrade the
local binaries. Try rebooting the newly added RTM node and see if it helps.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
"Justin Hoffmann" <Justin Hoffmann@.discussions.microsoft.com> wrote in
message news:A214ED19-F6CD-4D25-90CE-0A1D456750BD@.microsoft.com...
>I have recently had to rebuild my SQL Server 2000 sp3a 2 node
>active/passive
> cluster running on Windows 2000 AS SP4. We ran into issues about two
> weeks
> ago after a SAN migration (I'll spare all the gory details). When my
> previous cluster died, I used one of the nodes as a stand alone instance
> of
> SQL Server (to run our production database). On the other former node, I
> removed the OS clustering software and had to manually remove SQL Server.
> I
> eventually (with the assistance of Donna L. at MS) was able to get a
> single
> node cluster of SQL2K running on physical server PRODSQL01 (the virtual
> server name is PRODSQLCL01). While the cluster was running as a single
> node
> cluster, I applied sp3a and the 818 hotfix. I then migrated the data from
> the stand alone instance to PRODSQLCL01 and started to use it for
> production.
> I turned my attention to the other box and removed and reinstalled the
> Windows 2000 cluster software. This box is now called PRODSQL02. I was
> able
> to add PRODSQL02 to the windows cluster, and the successfully added it via
> SQL Server setup to the virtual server. My issue now is that PRODSQL02
> has
> the RTM versions of the binaries. I am not sure if I have a setup issue
> or I
> misunderstand point 3.10 of the sp3a readme. Currently the virtual server
> is
> running on PRODSQL01. If I attempt follow the steps under "If you need to
> rebuild a node in the failover cluster..." from PRODSQL02 I am only able
> to
> select the Virtual Server, and if I continue setup I get this error "all
> cluster disks available to this virtual server are owned by other node(s)"
> and then "Setup was unable to verify the state of the server for an
> upgrade.
> Verify the server is able to start and that you provided a valid sa
> password
> and restart setup". I understand that the virtual resources are only
> available on the currently active node, but the way I read the
> instructions I
> should be able to run the service pack installation on the inactive node.
> Do
> I need to rerun the SP (and hotfix) setup on SQL01 (since the virtual
> server
> is running there)? Do I need to move the resources to SQL02 and run the
> SP
> setup there? I just need clarification of where to run the SP setup since
> I
> just added SQL02 to this cluster.
>
|||Geoff:
I've rebooted the newly added RTM node several times and it doesn't seem to
help. When I launch SP3 setup (via setup.bat in the local sql2ksp3
directory) on the newly added RTM node I get to the screen that says Computer
Name. Local Computer is grayed out, there is a box for the existing Virtual
Server name. When I type the virtual server name in the box and press next,
I get the error messages I mentioned in my original post. Is there anything
else you can recommend?
Thanks,
Justin
"Geoff N. Hiten" wrote:

> You should be able to run setup on the non-host node and it will upgrade the
> local binaries. Try rebooting the newly added RTM node and see if it helps.
>
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
>
|||This is how I wound up fixing this:
I ran sp3a setup from PRODSQL01, which was the machine in control of the SQL
Virtual server at the time. It updated the binaries on PRODSQL02, but in
order to do so, the SQL Server service was stopped. Once sp3a setup
completed, I had to reboot PRODSQL02. When it was back up, I verified the
version of the sqlservr.exe file, and it was 8.00.760 (right click,
properties, version). Once I established that sp3a took on the newly added
node, I started the setup for the 8.00.818 security hotfix. SQL Server went
down briefly again, and then the binaries on the newly added box were
updated. I then installed MDAC 2.8 on this node and rebooted. Once
PRODSQL02 was running again I tested moving the cluster resources from 01 to
02. It succeeded. While SQL was running on 02 I ran throught setting up
Imceda SQL Lite Speed (again, it was on 01 but not 02). Once that completed,
I was able to verify that my normally scheduled transaction log backups
completed successfully. Both machines run SQL Server and perform the
backups correctly. I am not sure about the root cause of the issue I
encountered with not being able to run the sp and hotfix on the newly added
node when it wasn't running the Virtual SQL Server (the sp3a readme seems to
indicate that you can), but I finally have a 2 node active passive cluster
running again.
|||Just to clarify, it is active passive, so only one node runs the Virtual SQL
Server at any time. I was trying to say that each node is able to run SQL
Server, and each node is able to run the SQL Lite Speed backups. I had been
concerned that somehow I would get PRODSQL02 all patched but then failing
over would not work correctly. Everything is working OK.
"Justin Hoffmann" wrote:

> This is how I wound up fixing this:
> I ran sp3a setup from PRODSQL01, which was the machine in control of the SQL
> Virtual server at the time. It updated the binaries on PRODSQL02, but in
> order to do so, the SQL Server service was stopped. Once sp3a setup
> completed, I had to reboot PRODSQL02. When it was back up, I verified the
> version of the sqlservr.exe file, and it was 8.00.760 (right click,
> properties, version). Once I established that sp3a took on the newly added
> node, I started the setup for the 8.00.818 security hotfix. SQL Server went
> down briefly again, and then the binaries on the newly added box were
> updated. I then installed MDAC 2.8 on this node and rebooted. Once
> PRODSQL02 was running again I tested moving the cluster resources from 01 to
> 02. It succeeded. While SQL was running on 02 I ran throught setting up
> Imceda SQL Lite Speed (again, it was on 01 but not 02). Once that completed,
> I was able to verify that my normally scheduled transaction log backups
> completed successfully. Both machines run SQL Server and perform the
> backups correctly. I am not sure about the root cause of the issue I
> encountered with not being able to run the sp and hotfix on the newly added
> node when it wasn't running the Virtual SQL Server (the sp3a readme seems to
> indicate that you can), but I finally have a 2 node active passive cluster
> running again.
|||The current correct term is "Single-Instance". "Active-Active" and its
cousins all refer to technology used specifically in SQL server 7.0 only.
Sometimes the binary only upgrade doesn't work right. Your solution is the
fallback solution but it does have the obvious downside of taking the SQL
server offline for a short time during the upgrade.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Adminstrator
"Justin Hoffmann" <JustinHoffmann@.discussions.microsoft.com> wrote in
message news:DA3E156A-EAFD-45D9-B72E-AB4A657D53A0@.microsoft.com...[vbcol=seagreen]
> Just to clarify, it is active passive, so only one node runs the Virtual
> SQL
> Server at any time. I was trying to say that each node is able to run SQL
> Server, and each node is able to run the SQL Lite Speed backups. I had
> been
> concerned that somehow I would get PRODSQL02 all patched but then failing
> over would not work correctly. Everything is working OK.
> "Justin Hoffmann" wrote:

Receiving this error since migrating to SQL 2000 from SQL 7

Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
once a day while running jobs through SQL Agent. It may not be the same job
having the problem. Any thoughts?
Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
(80004005); Provider Error: 0 (0) Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL Server Help file:
Help context: 0. Process Exit Code 1. The step failed.
I have ran the jobs numerous times with DTS and they do not fail. I have run
the sp_updatestats on all databases on this server and I have turned on
logging with DTS and this job does not log anything when I get the timeout
message. Thanks for any other advice you can give. My customer is getting
very frustrated that this keeps not running.
"Connie" wrote:

> Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
> once a day while running jobs through SQL Agent. It may not be the same job
> having the problem. Any thoughts?
> Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
> (80004005); Provider Error: 0 (0) Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.

Receiving this error since migrating to SQL 2000 from SQL 7

Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
once a day while running jobs through SQL Agent. It may not be the same job
having the problem. Any thoughts?
Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
(80004005); Provider Error: 0 (0) Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL Server Help file:
Help context: 0. Process Exit Code 1. The step failed.Three simple suggestions:
1- Run the DTS package manually and see where (Which step)
you get the error.
2- Create an output file through Package-->Properties--
>Logging in the DTS package and read the output file for
the error.
3- If you upgraded from SQL Server 7.0 to 2000, run
sp_updatestats stored proc for all the databases in the QA.
>--Original Message--
>Ever since migrating to SQL 2000 from SQL 7 I receive
this error at least
>once a day while running jobs through SQL Agent. It may
not be the same job
>having the problem. Any thoughts?
>Executed as user: domain\user. DTSRun: Loading...
Error: -2147467259
>(80004005); Provider Error: 0 (0) Error string:
Timeout expired
>Error source: Microsoft OLE DB Provider for SQL
Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.
>.
>|||The job is only failing once or twice a day even though it runs every hour or
in the case of another job, every 1/2 hour. It is never the same time of
day. I can run the DTS job manually and it work without failing. I will
give the logging a try and the sp_updatestats. I didn't upgrade the server -
it was a clean install and a restore from SQL 7. Thanks for your help
"Mark" wrote:
> Three simple suggestions:
> 1- Run the DTS package manually and see where (Which step)
> you get the error.
> 2- Create an output file through Package-->Properties--
> >Logging in the DTS package and read the output file for
> the error.
> 3- If you upgraded from SQL Server 7.0 to 2000, run
> sp_updatestats stored proc for all the databases in the QA.
>
>
> >--Original Message--
> >Ever since migrating to SQL 2000 from SQL 7 I receive
> this error at least
> >once a day while running jobs through SQL Agent. It may
> not be the same job
> >having the problem. Any thoughts?
> >
> >Executed as user: domain\user. DTSRun: Loading...
> Error: -2147467259
> >(80004005); Provider Error: 0 (0) Error string:
> Timeout expired
> >Error source: Microsoft OLE DB Provider for SQL
> Server Help file:
> > Help context: 0. Process Exit Code 1. The step failed.
> >.
> >
>|||I have ran the jobs numerous times with DTS and they do not fail. I have run
the sp_updatestats on all databases on this server and I have turned on
logging with DTS and this job does not log anything when I get the timeout
message. Thanks for any other advice you can give. My customer is getting
very frustrated that this keeps not running.
"Connie" wrote:
> Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
> once a day while running jobs through SQL Agent. It may not be the same job
> having the problem. Any thoughts?
> Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
> (80004005); Provider Error: 0 (0) Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.sql

Receiving Error: 'QUOTED_IDENTIFIER' when updating

Hello, I am getting the following message when running a stored proc:
Server: Msg 1934, Level 16, State 1, Procedure SZ_ProcessToCPInvoices, Line
261
UPDATE failed because the following SET options have incorrect settings:
'QUOTED_IDENTIFIER'.
I cannot find any information about this error. This happens with
QUOTED_IDENTIFIER on or off.Ric,
Try going to Query Analyzer and editing the sp. You should be able to see
the settings of "QUOTED_IDENTIFIER" when the sp was created. chnage it to
accomodate your needs.
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO
ALTER procedure dbo.SZ_ProcessToCPInvoices
...
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
AMB
"Ric" wrote:

> Hello, I am getting the following message when running a stored proc:
> Server: Msg 1934, Level 16, State 1, Procedure SZ_ProcessToCPInvoices, Lin
e
> 261
> UPDATE failed because the following SET options have incorrect settings:
> 'QUOTED_IDENTIFIER'.
> I cannot find any information about this error. This happens with
> QUOTED_IDENTIFIER on or off.
>

Receiving Error: 'QUOTED_IDENTIFIER' when updating

Hello, I am getting the following message when running a stored proc:
Server: Msg 1934, Level 16, State 1, Procedure SZ_ProcessToCPInvoices, Line
261
UPDATE failed because the following SET options have incorrect settings:
'QUOTED_IDENTIFIER'.
I cannot find any information about this error. This happens with
QUOTED_IDENTIFIER on or off.
Ric,
Try going to Query Analyzer and editing the sp. You should be able to see
the settings of "QUOTED_IDENTIFIER" when the sp was created. chnage it to
accomodate your needs.
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO
ALTER procedure dbo.SZ_ProcessToCPInvoices
...
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
AMB
"Ric" wrote:

> Hello, I am getting the following message when running a stored proc:
> Server: Msg 1934, Level 16, State 1, Procedure SZ_ProcessToCPInvoices, Line
> 261
> UPDATE failed because the following SET options have incorrect settings:
> 'QUOTED_IDENTIFIER'.
> I cannot find any information about this error. This happens with
> QUOTED_IDENTIFIER on or off.
>

receive notification from server in application

Hello, I have an application which is running on multiple computers and is connected with one sql server. I would like to that the user is notified when another user is performing some special action. So I thought that when this action begins, the server is notified either by writing some data in a table or something like this. Then I would like other applications to be notified so is possible that notification service notifies the application? If yes how? ThanksSSNS may be used in instances like this.

If your "special actions" are not recognizable using the built-in event providers (SQL Server Event Provider & File System Event Provider), you'll need to create a custom event provider to gather the event data.

Assuming the criteria by which people want to be notified is fairly static, you can create subscriptions to match upon. SSNS is not a good choice if the criteria changes frequently (for example, I want to notified when the data behind the web page I'm looking at happens to change. People may bounce among web pages frequently so SSNS is not a good choice there.)

You'll definitely need to create a custom delivery protocol (and perhaps a custom content formatter too) to get the notification to the application.

BTW - you may also want to check out Query Notifications. That technology may offer some of the features you are looking for.

HTH...

Joe|||I want the users of the application to be notified when a particular field in particular table changes. How can the server find all the instances of my application that are connected to it and how can it send the information? How can my application receive them? Thanks

receive notification from server in application

Hello, I have an application which is running on multiple computers and is connected with one sql server. I would like to that the user is notified when another user is performing some special action. So I thought that when this action begins, the server is notified either by writing some data in a table or something like this. Then I would like other applications to be notified so is possible that notification service notifies the application? If yes how? Thanks
SSNS may be used in instances like this.

If your "special actions" are not recognizable using the built-in event providers (SQL Server Event Provider & File System Event Provider), you'll need to create a custom event provider to gather the event data.

Assuming the criteria by which people want to be notified is fairly static, you can create subscriptions to match upon. SSNS is not a good choice if the criteria changes frequently (for example, I want to notified when the data behind the web page I'm looking at happens to change. People may bounce among web pages frequently so SSNS is not a good choice there.)

You'll definitely need to create a custom delivery protocol (and perhaps a custom content formatter too) to get the notification to the application.

BTW - you may also want to check out Query Notifications. That technology may offer some of the features you are looking for.

HTH...

Joe|||I want the users of the application to be notified when a particular field in particular table changes. How can the server find all the instances of my application that are connected to it and how can it send the information? How can my application receive them? Thanks

Receive Error: 17805 Invalid buffer received from client

Hello
I am running SQL Server 2000 with SP 4 on Windows Server 2003. Every hour I
receive several notifications with the following:
Reply: Message not found. Insertion strings:Error: 17805, Severity: 20,
State: 3 Invalid buffer received from client.
I want to create a SQL Profiler trace that will help me to identify which
sql statements \ stored procedures are causing this error. What will i need
to specify in the trace to identify the transaction that is causing this
error?
Please advise..
Cheers!
BrettSee response in microsoft.public.sqlserver.clients
-Sue
On Fri, 21 Oct 2005 13:50:53 -0700, "Brett Davis"
<bdavis123@.cox.net> wrote:

>Hello
>I am running SQL Server 2000 with SP 4 on Windows Server 2003. Every hour
I
>receive several notifications with the following:
> Reply: Message not found. Insertion strings:Error: 17805, Severity: 20,
>State: 3 Invalid buffer received from client.
>I want to create a SQL Profiler trace that will help me to identify which
>sql statements \ stored procedures are causing this error. What will i nee
d
>to specify in the trace to identify the transaction that is causing this
>error?
>Please advise..
>Cheers!
>Brett
>

Receive Error: 17805 Invalid buffer received from client

Hello
I am running SQL Server 2000 with SP 4 on Windows Server 2003. Every hour I
receive several notifications with the following:
Reply: Message not found. Insertion strings:Error: 17805, Severity: 20,
State: 3 Invalid buffer received from client.
I want to create a SQL Profiler trace that will help me to identify which
sql statements \ stored procedures are causing this error. What will i need
to specify in the trace to identify the transaction that is causing this
error and what kind of filter if any do i need to apply?
Please advise..
Cheers!
Brett
You should be able to track it down quickly if it's
happening every hour. You get capture exceptions using the
Errors and Warnings class. You can then see the spid that
generated this error. If you also capture the T-SQL
statements and stored procedures at the same time, you will
see what the spid that generated the exception was
executing.
What you filter on depends more on your system. You can at
least filter out the applications SQL Profiler and SQLAgent%
-Sue
On Fri, 21 Oct 2005 15:33:20 -0700, "Brett Davis"
<bdavis123@.cox.net> wrote:

>Hello
>I am running SQL Server 2000 with SP 4 on Windows Server 2003. Every hour I
>receive several notifications with the following:
> Reply: Message not found. Insertion strings:Error: 17805, Severity: 20,
> State: 3 Invalid buffer received from client.
>I want to create a SQL Profiler trace that will help me to identify which
>sql statements \ stored procedures are causing this error. What will i need
>to specify in the trace to identify the transaction that is causing this
>error and what kind of filter if any do i need to apply?
>Please advise..
>Cheers!
>Brett
>

Receive Error: 17805 Invalid buffer received from client

Hello
I am running SQL Server 2000 with SP 4 on Windows Server 2003. Every hour I
receive several notifications with the following:
Reply: Message not found. Insertion strings:Error: 17805, Severity: 20,
State: 3 Invalid buffer received from client.
I want to create a SQL Profiler trace that will help me to identify which
sql statements \ stored procedures are causing this error. What will i need
to specify in the trace to identify the transaction that is causing this
error?
Please advise..
Cheers!
Brett
See response in microsoft.public.sqlserver.clients
-Sue
On Fri, 21 Oct 2005 13:50:53 -0700, "Brett Davis"
<bdavis123@.cox.net> wrote:

>Hello
>I am running SQL Server 2000 with SP 4 on Windows Server 2003. Every hour I
>receive several notifications with the following:
> Reply: Message not found. Insertion strings:Error: 17805, Severity: 20,
>State: 3 Invalid buffer received from client.
>I want to create a SQL Profiler trace that will help me to identify which
>sql statements \ stored procedures are causing this error. What will i need
>to specify in the trace to identify the transaction that is causing this
>error?
>Please advise..
>Cheers!
>Brett
>
sql

recbase.cpp error

Can anyone help me with this error? The query that is causing this
problem was running like a champ up until about 4 days ago. I have done no
upgrades to the database server in the last couple weeks. Thanks.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 10/6/2003
Time: 12:08:48 PM
User: N/A
Computer: DATASERVERA
Description:
17066 :
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
-dougI found this in an old post...
This looks bad. An assertion error is a check that a programmer puts
into his code to verify that assumptions in his code are true. If they
are not, abortion is executed to prevent even more serious accidents.
(Data corruption is after all worse than a hanging or crashing server.)
Now, the assertion 'FALSE' is a little funny. Looks like a "we are not
supposed to come here".
If this happen to you more than once, I would recommend that you open a
case with Microsoft. They may know about the problem and have a workaround.
In any case, since this clearly is a bug in SQL Server, any fee that
you have to pay initially should be refunded.
--
HTH
Ryan Waight, MCDBA, MCSE
"Doug Threewitt" <doug@.seisystems.com> wrote in message
news:%23lK4EhDjDHA.488@.TK2MSFTNGP09.phx.gbl...
> Can anyone help me with this error? The query that is causing this
> problem was running like a champ up until about 4 days ago. I have done
no
> upgrades to the database server in the last couple weeks. Thanks.
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17055
> Date: 10/6/2003
> Time: 12:08:48 PM
> User: N/A
> Computer: DATASERVERA
> Description:
> 17066 :
> SQL Server Assertion: File: <recbase.cpp>, line=1378
> Failed Assertion = 'm_offBeginVar < m_SizeRec'.
>
> -doug
>|||This usually points to hardware-caused corruption in your database. The
assert is basically saying that a record on a page is corrupt. You can
contact Product Support (http://support.microsoft.com) who will be able to
help or do the following:
1) run DBCC CHECKDB on the database to determine if any corruption is
present
2) check the NT event log and SQL Server errorlog for previous
errors/problems
3) run hardware diagnostics
4) if corruption is present, restore the database from your up-to-date
backups onto different hardware
Regards,
Paul.
--
Paul Randal
DBCC Technical Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Doug Threewitt" <doug@.seisystems.com> wrote in message
news:#lK4EhDjDHA.488@.TK2MSFTNGP09.phx.gbl...
> Can anyone help me with this error? The query that is causing this
> problem was running like a champ up until about 4 days ago. I have done
no
> upgrades to the database server in the last couple weeks. Thanks.
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17055
> Date: 10/6/2003
> Time: 12:08:48 PM
> User: N/A
> Computer: DATASERVERA
> Description:
> 17066 :
> SQL Server Assertion: File: <recbase.cpp>, line=1378
> Failed Assertion = 'm_offBeginVar < m_SizeRec'.
>
> -doug
>|||I've run DBCC CHECKDB on the database and it found no corruption. The event
log shows this error occuring a few other times. What hardware diagnostics
do you recommend running? Also, how can I find my PID for the SQL Server so
I can get some help from Microsoft regarding this matter. Thanks for all
your help
-doug
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:%23gO4Z2OjDHA.2160@.TK2MSFTNGP12.phx.gbl...
> This usually points to hardware-caused corruption in your database. The
> assert is basically saying that a record on a page is corrupt. You can
> contact Product Support (http://support.microsoft.com) who will be able to
> help or do the following:
> 1) run DBCC CHECKDB on the database to determine if any corruption is
> present
> 2) check the NT event log and SQL Server errorlog for previous
> errors/problems
> 3) run hardware diagnostics
> 4) if corruption is present, restore the database from your up-to-date
> backups onto different hardware
> Regards,
> Paul.
> --
> Paul Randal
> DBCC Technical Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Doug Threewitt" <doug@.seisystems.com> wrote in message
> news:#lK4EhDjDHA.488@.TK2MSFTNGP09.phx.gbl...
> > Can anyone help me with this error? The query that is causing this
> > problem was running like a champ up until about 4 days ago. I have done
> no
> > upgrades to the database server in the last couple weeks. Thanks.
> >
> > Event Type: Error
> > Event Source: MSSQLSERVER
> > Event Category: (2)
> > Event ID: 17055
> > Date: 10/6/2003
> > Time: 12:08:48 PM
> > User: N/A
> > Computer: DATASERVERA
> > Description:
> > 17066 :
> > SQL Server Assertion: File: <recbase.cpp>, line=1378
> > Failed Assertion = 'm_offBeginVar < m_SizeRec'.
> >
> >
> >
> > -doug
> >
> >
>|||Any disk, controller or IO subsystem diagnostics you can run. I don't know
about the PID.
There should also be some sqlXXXXX.dmp files in the same directory as the
errorlog which will be useful to PSS as they will have the call stacks at
the time the assert fires.
Regards,
Paul.
--
Paul Randal
DBCC Technical Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Doug Threewitt" <doug@.seisystems.com> wrote in message
news:#EAOl7QjDHA.2160@.TK2MSFTNGP10.phx.gbl...
> I've run DBCC CHECKDB on the database and it found no corruption. The
event
> log shows this error occuring a few other times. What hardware
diagnostics
> do you recommend running? Also, how can I find my PID for the SQL Server
so
> I can get some help from Microsoft regarding this matter. Thanks for all
> your help
>
> -doug
>
> "Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
> news:%23gO4Z2OjDHA.2160@.TK2MSFTNGP12.phx.gbl...
> > This usually points to hardware-caused corruption in your database. The
> > assert is basically saying that a record on a page is corrupt. You can
> > contact Product Support (http://support.microsoft.com) who will be able
to
> > help or do the following:
> > 1) run DBCC CHECKDB on the database to determine if any corruption is
> > present
> > 2) check the NT event log and SQL Server errorlog for previous
> > errors/problems
> > 3) run hardware diagnostics
> > 4) if corruption is present, restore the database from your up-to-date
> > backups onto different hardware
> >
> > Regards,
> >
> > Paul.
> >
> > --
> > Paul Randal
> > DBCC Technical Lead, Microsoft SQL Server Storage Engine
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > "Doug Threewitt" <doug@.seisystems.com> wrote in message
> > news:#lK4EhDjDHA.488@.TK2MSFTNGP09.phx.gbl...
> > > Can anyone help me with this error? The query that is causing
this
> > > problem was running like a champ up until about 4 days ago. I have
done
> > no
> > > upgrades to the database server in the last couple weeks. Thanks.
> > >
> > > Event Type: Error
> > > Event Source: MSSQLSERVER
> > > Event Category: (2)
> > > Event ID: 17055
> > > Date: 10/6/2003
> > > Time: 12:08:48 PM
> > > User: N/A
> > > Computer: DATASERVERA
> > > Description:
> > > 17066 :
> > > SQL Server Assertion: File: <recbase.cpp>, line=1378
> > > Failed Assertion = 'm_offBeginVar < m_SizeRec'.
> > >
> > >
> > >
> > > -doug
> > >
> > >
> >
> >
>|||Thanks for all your help. I found some corrupt indexes(sp.) that I believe
were causing me some difficulties.....
-doug
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:eJSuSMTjDHA.1132@.tk2msftngp13.phx.gbl...
> Any disk, controller or IO subsystem diagnostics you can run. I don't know
> about the PID.
> There should also be some sqlXXXXX.dmp files in the same directory as the
> errorlog which will be useful to PSS as they will have the call stacks at
> the time the assert fires.
> Regards,
> Paul.
> --
> Paul Randal
> DBCC Technical Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Doug Threewitt" <doug@.seisystems.com> wrote in message
> news:#EAOl7QjDHA.2160@.TK2MSFTNGP10.phx.gbl...
> > I've run DBCC CHECKDB on the database and it found no corruption. The
> event
> > log shows this error occuring a few other times. What hardware
> diagnostics
> > do you recommend running? Also, how can I find my PID for the SQL
Server
> so
> > I can get some help from Microsoft regarding this matter. Thanks for
all
> > your help
> >
> >
> > -doug
> >
> >
> > "Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
> > news:%23gO4Z2OjDHA.2160@.TK2MSFTNGP12.phx.gbl...
> > > This usually points to hardware-caused corruption in your database.
The
> > > assert is basically saying that a record on a page is corrupt. You can
> > > contact Product Support (http://support.microsoft.com) who will be
able
> to
> > > help or do the following:
> > > 1) run DBCC CHECKDB on the database to determine if any corruption is
> > > present
> > > 2) check the NT event log and SQL Server errorlog for previous
> > > errors/problems
> > > 3) run hardware diagnostics
> > > 4) if corruption is present, restore the database from your up-to-date
> > > backups onto different hardware
> > >
> > > Regards,
> > >
> > > Paul.
> > >
> > > --
> > > Paul Randal
> > > DBCC Technical Lead, Microsoft SQL Server Storage Engine
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > "Doug Threewitt" <doug@.seisystems.com> wrote in message
> > > news:#lK4EhDjDHA.488@.TK2MSFTNGP09.phx.gbl...
> > > > Can anyone help me with this error? The query that is causing
> this
> > > > problem was running like a champ up until about 4 days ago. I have
> done
> > > no
> > > > upgrades to the database server in the last couple weeks. Thanks.
> > > >
> > > > Event Type: Error
> > > > Event Source: MSSQLSERVER
> > > > Event Category: (2)
> > > > Event ID: 17055
> > > > Date: 10/6/2003
> > > > Time: 12:08:48 PM
> > > > User: N/A
> > > > Computer: DATASERVERA
> > > > Description:
> > > > 17066 :
> > > > SQL Server Assertion: File: <recbase.cpp>, line=1378
> > > > Failed Assertion = 'm_offBeginVar < m_SizeRec'.
> > > >
> > > >
> > > >
> > > > -doug
> > > >
> > > >
> > >
> > >
> >
> >
>

Rebuilding master with multiple instances

When having to rebuild the master database (using SQL 2K), and their is
more than one instance of SQL Server running, how do you specify the
appropriate instance to rebuild?
Message posted via http://www.sqlmonster.com
I believe SERVER is one of the parameters.
Sincerely,
Anthony Thomas

"Robert Richards via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:4d7df593846d4924bd55c0797e2e9544@.SQLMonster.c om...
When having to rebuild the master database (using SQL 2K), and their is
more than one instance of SQL Server running, how do you specify the
appropriate instance to rebuild?
Message posted via http://www.sqlmonster.com

Rebuilding master with multiple instances

When having to rebuild the master database (using SQL 2K), and their is
more than one instance of SQL Server running, how do you specify the
appropriate instance to rebuild?
Message posted via http://www.droptable.comI believe SERVER is one of the parameters.
Sincerely,
Anthony Thomas
"Robert Richards via droptable.com" <forum@.droptable.com> wrote in message
news:4d7df593846d4924bd55c0797e2e9544@.SQ
droptable.com...
When having to rebuild the master database (using SQL 2K), and their is
more than one instance of SQL Server running, how do you specify the
appropriate instance to rebuild?
Message posted via http://www.droptable.com

Rebuilding master with multiple instances

When having to rebuild the master database (using SQL 2K), and their is
more than one instance of SQL Server running, how do you specify the
appropriate instance to rebuild?
--
Message posted via http://www.sqlmonster.comI believe SERVER is one of the parameters.
Sincerely,
Anthony Thomas
"Robert Richards via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:4d7df593846d4924bd55c0797e2e9544@.SQLMonster.com...
When having to rebuild the master database (using SQL 2K), and their is
more than one instance of SQL Server running, how do you specify the
appropriate instance to rebuild?
--
Message posted via http://www.sqlmonster.comsql

Rebuild one node from SQL Cluster

hi guys,
I have SQL Cluster running on 2 servers running on Win2k3. The SQL Cluster
is on Active/Passive config. One of the node giving problem and i am planning
to rebuild it until this question strikes my mind. After rebuild, how do i
join back to existing SQL Cluster?
TIA
oh...it's k...i got it
http://www.microsoft.com/technet/pro...rt4/c1261.mspx
"Adding or Removing a Cluster Node from the Virtual Server Definition
Another new feature of SQL Server 2000 failover clustering is the ability to
add or remove a cluster node from a SQL Server virtual server definition.
Adding nodes to the existing SQL Server virtual server definition performs
all the necessary operations on the new nodes (including installing binaries,
system components, and creating services) and performs the necessary
modifications to the cluster configuration. "
"rupart" wrote:

> hi guys,
> I have SQL Cluster running on 2 servers running on Win2k3. The SQL Cluster
> is on Active/Passive config. One of the node giving problem and i am planning
> to rebuild it until this question strikes my mind. After rebuild, how do i
> join back to existing SQL Cluster?
> TIA
|||You'll get the right audience looking at this if you plst to
ms.p.sqlserver.clustering.
There are these links
http://www.microsoft.com/technet/pro.../failclus.mspx
http://www.microsoft.com/downloads/d...displaylang=en
http://www.sql-server-performance.co...stall_main.asp
http://support.microsoft.com/?kbid=301600
Which should help but some questions first.
What SP level is the OS and SQL currently at?
There are issues adding back failed nodes to SP4 level (I had them).
Also you must follow certain guidelines when evicting/adding nodes otherwise
you could render your cluster unusable.
Also have a backup plan in case this actually does happen. I restored the
critical databases to another cluster just prior to doing the actual work on
a live system just in case it all went wrong.
Also if you have access to a "virtual server system" Virtual Server 2005 or
VMWare create a system similar to you current one to try the process out.
Nik Marshall-Blank MCSD/MCDBA
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:7BE08633-F659-4B34-9F5E-806A3550CA02@.microsoft.com...
> hi guys,
> I have SQL Cluster running on 2 servers running on Win2k3. The SQL Cluster
> is on Active/Passive config. One of the node giving problem and i am
> planning
> to rebuild it until this question strikes my mind. After rebuild, how do i
> join back to existing SQL Cluster?
> TIA

Rebuild one node from SQL Cluster

hi guys,
I have SQL Cluster running on 2 servers running on Win2k3. The SQL Cluster
is on Active/Passive config. One of the node giving problem and i am planning
to rebuild it until this question strikes my mind. After rebuild, how do i
join back to existing SQL Cluster?
TIAoh...it's k...i got it
http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part4/c1261.mspx
"Adding or Removing a Cluster Node from the Virtual Server Definition
Another new feature of SQL Server 2000 failover clustering is the ability to
add or remove a cluster node from a SQL Server virtual server definition.
Adding nodes to the existing SQL Server virtual server definition performs
all the necessary operations on the new nodes (including installing binaries,
system components, and creating services) and performs the necessary
modifications to the cluster configuration. "
"rupart" wrote:
> hi guys,
> I have SQL Cluster running on 2 servers running on Win2k3. The SQL Cluster
> is on Active/Passive config. One of the node giving problem and i am planning
> to rebuild it until this question strikes my mind. After rebuild, how do i
> join back to existing SQL Cluster?
> TIA|||You'll get the right audience looking at this if you plst to
ms.p.sqlserver.clustering.
There are these links
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx
http://www.microsoft.com/downloads/details.aspx?FamilyID=96f76ed7-9634-4300-9159-89638f4b4ef7&displaylang=en
http://www.sql-server-performance.com/sqlserver2000_clustering_install_main.asp
http://support.microsoft.com/?kbid=301600
Which should help but some questions first.
What SP level is the OS and SQL currently at?
There are issues adding back failed nodes to SP4 level (I had them).
Also you must follow certain guidelines when evicting/adding nodes otherwise
you could render your cluster unusable.
Also have a backup plan in case this actually does happen. I restored the
critical databases to another cluster just prior to doing the actual work on
a live system just in case it all went wrong.
Also if you have access to a "virtual server system" Virtual Server 2005 or
VMWare create a system similar to you current one to try the process out.
--
Nik Marshall-Blank MCSD/MCDBA
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:7BE08633-F659-4B34-9F5E-806A3550CA02@.microsoft.com...
> hi guys,
> I have SQL Cluster running on 2 servers running on Win2k3. The SQL Cluster
> is on Active/Passive config. One of the node giving problem and i am
> planning
> to rebuild it until this question strikes my mind. After rebuild, how do i
> join back to existing SQL Cluster?
> TIAsql

Rebuild one node from SQL Cluster

hi guys,
I have SQL Cluster running on 2 servers running on Win2k3. The SQL Cluster
is on Active/Passive config. One of the node giving problem and i am plannin
g
to rebuild it until this question strikes my mind. After rebuild, how do i
join back to existing SQL Cluster?
TIAoh...it's k...i got it
[url]http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part4/c1261.mspx[/url
]
"Adding or Removing a Cluster Node from the Virtual Server Definition
Another new feature of SQL Server 2000 failover clustering is the ability to
add or remove a cluster node from a SQL Server virtual server definition.
Adding nodes to the existing SQL Server virtual server definition performs
all the necessary operations on the new nodes (including installing binaries
,
system components, and creating services) and performs the necessary
modifications to the cluster configuration. "
"rupart" wrote:

> hi guys,
> I have SQL Cluster running on 2 servers running on Win2k3. The SQL Cluster
> is on Active/Passive config. One of the node giving problem and i am plann
ing
> to rebuild it until this question strikes my mind. After rebuild, how do i
> join back to existing SQL Cluster?
> TIA|||You'll get the right audience looking at this if you plst to
ms.p.sqlserver.clustering.
There are these links
http://www.microsoft.com/technet/pr...n/failclus.mspx
http://www.microsoft.com/downloads/...&displaylang=en
http://www.sql-server-performance.c...om/?kbid=301600
Which should help but some questions first.
What SP level is the OS and SQL currently at?
There are issues adding back failed nodes to SP4 level (I had them).
Also you must follow certain guidelines when evicting/adding nodes otherwise
you could render your cluster unusable.
Also have a backup plan in case this actually does happen. I restored the
critical databases to another cluster just prior to doing the actual work on
a live system just in case it all went wrong.
Also if you have access to a "virtual server system" Virtual Server 2005 or
VMWare create a system similar to you current one to try the process out.
Nik Marshall-Blank MCSD/MCDBA
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:7BE08633-F659-4B34-9F5E-806A3550CA02@.microsoft.com...
> hi guys,
> I have SQL Cluster running on 2 servers running on Win2k3. The SQL Cluster
> is on Active/Passive config. One of the node giving problem and i am
> planning
> to rebuild it until this question strikes my mind. After rebuild, how do i
> join back to existing SQL Cluster?
> TIA

Rebuild of SQL Server

With the initial system DISK configuration now running out of space, it will
be necessary to reconfigure the disk structure - with a reload of Win2k and
SQL 2000.
Question: Prior to the server rebuild, if SQL is stopped and system/user d
atabase device files are copied to tape, after the rebuild of the server (sa
me name) and a reload of SQL 2000 to same drive, would it possible to stop S
QL and copy the same databa
se device files from tape to avoid a SQL restore of the databases. This woul
d save some time and effort in recreating the databases from scratch, includ
ing the master database.
Thanks in Advance for any advice.Hi,
Yes, You can do that and it will be the faster and easy methodology. But
ensure that you have the same service pack in new server as well.
Thanks
Hari
MCDBA
Thanks
Hari
MCDBA
"Greg H" <anonymous@.discussions.microsoft.com> wrote in message
news:F5F90AF5-EA63-4192-BEB5-E4238C2A624F@.microsoft.com...
> With the initial system DISK configuration now running out of space, it
will be necessary to reconfigure the disk structure - with a reload of Win2k
and SQL 2000.
> Question: Prior to the server rebuild, if SQL is stopped and system/user
database device files are copied to tape, after the rebuild of the server
(same name) and a reload of SQL 2000 to same drive, would it possible to
stop SQL and copy the same database device files from tape to avoid a SQL
restore of the databases. This would save some time and effort in recreating
the databases from scratch, including the master database.
> Thanks in Advance for any advice.|||Provided all the path namews for location of master, model, tempdb etc =
and the user databses are the same, same service pack levels etc then I =
be;leive this should be OK. I would still test it though.=20
Being paranoid I would take at least 2 tape copies. And if possible =
restore to new disks BEFORE ditching the old ones.
But do you really ned to reinstall win2k to make the disk changes.?
Mike John
"Greg H" <anonymous@.discussions.microsoft.com> wrote in message =
news:F5F90AF5-EA63-4192-BEB5-E4238C2A624F@.microsoft.com...
> With the initial system DISK configuration now running out of space, =
it will be necessary to reconfigure the disk structure - with a reload =
of Win2k and SQL 2000. =20
> Question: Prior to the server rebuild, if SQL is stopped and =
system/user database device files are copied to tape, after the rebuild =
of the server (same name) and a reload of SQL 2000 to same drive, would =
it possible to stop SQL and copy the same database device files from =
tape to avoid a SQL restore of the databases. This would save some time =
and effort in recreating the databases from scratch, including the =
master database.
>=20
> Thanks in Advance for any advice.

Rebuild of server--a few questions

Our IT support has decided it is necessary to do a complete rebuild of
a server that is running SQL Server 2005. I've looked at numerous
postings on how to bring the Server back up after the rebuild, but
because of certain factors in this rebuild I'm still unclear on the
best approach. The major changes that will take place include:
1. Renaming the Server and the SQL Server instance
2. Reconfiguring the storage to create a separate partition for the
transaction logs.
In this case would I still want/need to restore the backups of the
system databases?
My current plan is to:
Prior to the rebuild:
1.Run a full back-up of all databases including the system databases.
2.Run the sp_help_revlogin procedure to generate a script to recreate
the users
3.Detach the user databases and copy the database files to another
server and/or tape.
After the rebuild:
1.Install SQL Server and apply service packs
2.Start SQL Service and execute script to recreate the users.
3.Place the database files in the desired locations (e.g. place
transaction logs on mirrored drive)
4.Attach user databases.
I imagine the primary disadvantage to not restoring the system
databases is I will have to recreate the maintenance plans, but I had
planned on making changes to these plans and there are currently only
two.
Am I missing anything?
Thanks in advance
Cheryl
Sounds good , other factors would include whether applications are using the
dbs , also, if you have time you could try a test run
Jack Vamvas
___________________________________
Search IT jobs from multiple sources- http://www.ITjobfeed.com
<cbender@.mriresearch.org> wrote in message
news:35ff425a-ccc0-475d-812a-1f7762367885@.d5g2000hsc.googlegroups.com...
> Our IT support has decided it is necessary to do a complete rebuild of
> a server that is running SQL Server 2005. I've looked at numerous
> postings on how to bring the Server back up after the rebuild, but
> because of certain factors in this rebuild I'm still unclear on the
> best approach. The major changes that will take place include:
> 1. Renaming the Server and the SQL Server instance
> 2. Reconfiguring the storage to create a separate partition for the
> transaction logs.
> In this case would I still want/need to restore the backups of the
> system databases?
> My current plan is to:
> Prior to the rebuild:
> 1. Run a full back-up of all databases including the system databases.
> 2. Run the sp_help_revlogin procedure to generate a script to recreate
> the users
> 3. Detach the user databases and copy the database files to another
> server and/or tape.
> After the rebuild:
> 1. Install SQL Server and apply service packs
> 2. Start SQL Service and execute script to recreate the users.
> 3. Place the database files in the desired locations (e.g. place
> transaction logs on mirrored drive)
> 4. Attach user databases.
> I imagine the primary disadvantage to not restoring the system
> databases is I will have to recreate the maintenance plans, but I had
> planned on making changes to these plans and there are currently only
> two.
> Am I missing anything?
> Thanks in advance
> Cheryl
>

Rebuild of server--a few questions

Our IT support has decided it is necessary to do a complete rebuild of
a server that is running SQL Server 2005. I've looked at numerous
postings on how to bring the Server back up after the rebuild, but
because of certain factors in this rebuild I'm still unclear on the
best approach. The major changes that will take place include:
1. Renaming the Server and the SQL Server instance
2. Reconfiguring the storage to create a separate partition for the
transaction logs.
In this case would I still want/need to restore the backups of the
system databases?
My current plan is to:
Prior to the rebuild:
1. Run a full back-up of all databases including the system databases.
2. Run the sp_help_revlogin procedure to generate a script to recreate
the users
3. Detach the user databases and copy the database files to another
server and/or tape.
After the rebuild:
1. Install SQL Server and apply service packs
2. Start SQL Service and execute script to recreate the users.
3. Place the database files in the desired locations (e.g. place
transaction logs on mirrored drive)
4. Attach user databases.
I imagine the primary disadvantage to not restoring the system
databases is I will have to recreate the maintenance plans, but I had
planned on making changes to these plans and there are currently only
two.
Am I missing anything?
Thanks in advance
CherylSounds good , other factors would include whether applications are using the
dbs , also, if you have time you could try a test run
--
Jack Vamvas
___________________________________
Search IT jobs from multiple sources- http://www.ITjobfeed.com
<cbender@.mriresearch.org> wrote in message
news:35ff425a-ccc0-475d-812a-1f7762367885@.d5g2000hsc.googlegroups.com...
> Our IT support has decided it is necessary to do a complete rebuild of
> a server that is running SQL Server 2005. I've looked at numerous
> postings on how to bring the Server back up after the rebuild, but
> because of certain factors in this rebuild I'm still unclear on the
> best approach. The major changes that will take place include:
> 1. Renaming the Server and the SQL Server instance
> 2. Reconfiguring the storage to create a separate partition for the
> transaction logs.
> In this case would I still want/need to restore the backups of the
> system databases?
> My current plan is to:
> Prior to the rebuild:
> 1. Run a full back-up of all databases including the system databases.
> 2. Run the sp_help_revlogin procedure to generate a script to recreate
> the users
> 3. Detach the user databases and copy the database files to another
> server and/or tape.
> After the rebuild:
> 1. Install SQL Server and apply service packs
> 2. Start SQL Service and execute script to recreate the users.
> 3. Place the database files in the desired locations (e.g. place
> transaction logs on mirrored drive)
> 4. Attach user databases.
> I imagine the primary disadvantage to not restoring the system
> databases is I will have to recreate the maintenance plans, but I had
> planned on making changes to these plans and there are currently only
> two.
> Am I missing anything?
> Thanks in advance
> Cheryl
>