Failed Maintenance Plan

Please advice.
I run a SQL2k SP4 on WIN2K SP4.
I have a maintenance plan to backup the databases at 01:30AM. This has alway
s been succesfull.
Strangely it did the backup at 02:25PM with no entry in SQL Error Log and ca
using subsequent backups to fail as the files created had the 02:25 badge he
nce could not be deleted.
Please help as to what caused the maintenance plan to backup at 02:25 and wh
at to do to avoid it.
Thanks for your kind response.I posted a reply to this yesterday. Here's that text:
My guess is that it wasn't Main Plan that did the backup, someone else did i
t (or explicitly started the main
plan job, or scheduled the main plan job at that hour). If it was executed a
s a job, you can view the job
history under EM, Management, Jobs. In any event, each backup is written to
the eventlog and the errorlog
file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Timi" <anonymous@.discussions.microsoft.com> wrote in message
news:EA0A7329-EAA1-49B3-9DDB-1736B6F35A4C@.microsoft.com...
> Please advice.
> I run a SQL2k SP4 on WIN2K SP4.
> I have a maintenance plan to backup the databases at 01:30AM. This has alw
ays been succesfull.
> Strangely it did the backup at 02:25PM with no entry in SQL Error Log and causing
subsequent backups to fail
as the files created had the 02:25 badge hence could not be deleted.
> Please help as to what caused the maintenance plan to backup at 02:25 and
what to do to avoid it.
> Thanks for your kind response.
>|||Thanks for your response.
The maint plan was ran at 02:25AM as opposed to 01:30AM the scheduled time.|||can you check with your server guys if there was a problem
with the server which resulted in it being restarted on or
arounf 2:25 ?, but the best way of finding out is to check
the error log.
J

>--Original Message--
>Thanks for your response.
>The maint plan was ran at 02:25AM as opposed to 01:30AM
the scheduled time.
>.
>|||Agent does no run a job if it was down at the time it should have executed.
I doubt that this is the reason,
based on that. I bet a beer that someone started the job at that time.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Julie" <anonymous@.discussions.microsoft.com> wrote in message news:13fdd01c41357$84085e80$
a301280a@.phx.gbl...
> can you check with your server guys if there was a problem
> with the server which resulted in it being restarted on or
> arounf 2:25 ?, but the best way of finding out is to check
> the error log.
> J
>
> the scheduled time.|||Bet a beer against you and your SQL Server knowledge, never ;)
Anyway your right but my sneaky plan was to get Timm to check the server, as
we both agree thats where the problem is, and who actually started it.|||:-)
<<as we both agree thats where the problem is, and who actually started it.>
>
Yep.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:D6CB3367-9F9F-4633-B7FE-3FBEBFFA8B74@.microsoft.com...
> Bet a beer against you and your SQL Server knowledge, never ;)
> Anyway your right but my sneaky plan was to get Timm to check the server, as we bo
th agree thats where the
problem is, and who actually started it.

Failed Maintenance Plan

Please advice.
I run a SQL2k SP4 on WIN2K SP4.
I have a maintenance plan to backup the databases at 01:30AM. This has alway
s been successfull.
Strangely it did the backup at 02:25PM with no entry in SQL Error Log and ca
using subsequent backups to fail as the files created had the 02:25 badge he
nce could not be deleted.
Please help as to what caused the maintenece plan to backup at 02:25 and wha
t to do to avoid it.
Thanks for your kind response.My guess is that it wasn't Main Plan that did the backup, someone else did i
t (or explicitly started the main
plan job, or scheduled the main plan job at that hour). If it was executed a
s a job, you can view the job
history under EM, Management, Jobs. In any event, each backup is written to
the eventlog and the errorlog
file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Timi" <anonymous@.discussions.microsoft.com> wrote in message
news:CDA33615-5054-47D3-8D06-0A52B8FB7544@.microsoft.com...
> Please advice.
> I run a SQL2k SP4 on WIN2K SP4.
> I have a maintenance plan to backup the databases at 01:30AM. This has alw
ays been successfull.
> Strangely it did the backup at 02:25PM with no entry in SQL Error Log and causing
subsequent backups to fail
as the files created had the 02:25 badge hence could not be deleted.
> Please help as to what caused the maintenece plan to backup at 02:25 and w
hat to do to avoid it.
> Thanks for your kind response.
>

fail to install sql server 7.0 to window2000 server cluster

we have a 2 nodes win2k server cluster which installed sqlsrv 7.0, the
primary one failed, and the secondary take over the service as design.
we do not have system backup for the primary node, and we got a blue screen
for that one. it seams like that some registe records are crashed. we decide
to reinstall that node.
when we install sql server before cluster service, the cluster service will
complain the sql server's exsiting. when we install the cluster before sql
server 7.0, the sql server will complain we should undeploy the cluster.
i can not find any valueable resources for install sql server 7.0 in win2k
cluster. is there any one had this situation before?
Unfortunately, you will have to rebuild your SS70 cluster. This does not
mean you will have to rebuild your installation, just the cluster.
Uncluster the current node.
Add the new node to the Win2K cluster.
Rerun Comclust to cluster the MS DTC on the new node.
Install SS70 on the new node.
Recluster the SS70 installation.
Anthony Thomas

"linbiao" <linbiao@.discussions.microsoft.com> wrote in message
news:2133DDC4-EDDF-4023-B381-9AA778CDC567@.microsoft.com...
> we have a 2 nodes win2k server cluster which installed sqlsrv 7.0, the
> primary one failed, and the secondary take over the service as design.
> we do not have system backup for the primary node, and we got a blue
screen
> for that one. it seams like that some registe records are crashed. we
decide
> to reinstall that node.
> when we install sql server before cluster service, the cluster service
will
> complain the sql server's exsiting. when we install the cluster before sql
> server 7.0, the sql server will complain we should undeploy the cluster.
> i can not find any valueable resources for install sql server 7.0 in win2k
> cluster. is there any one had this situation before?
|||On Sun, 17 Dec 2006 15:21:50 -0800, Anthony Thomas <ALThomas@.kc.rr.com>
wrote:

> Unfortunately, you will have to rebuild your SS70 cluster. This does not
> mean you will have to rebuild your installation, just the cluster.
> Uncluster the current node.
> Add the new node to the Win2K cluster.
> Rerun Comclust to cluster the MS DTC on the new node.
> Install SS70 on the new node.
> Recluster the SS70 installation.
>
> Anthony Thomas
>
thank you very much. we will try it.
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Extremely Slow connection time

Hi
I have recently reinstalled XP Professional as well as the MSSQL client tool
s.
Our SQL 2000 server is running Win2K with 512MB RAM, and has been doing so f
or quite a while, no changes where done to the server while I reinstalled XP
on my PC.
Now my connection to the SQL server is extremely sluggish, e.g. connecting v
ia the Query Analyzer takes up to 2 minutes, and so do any other subsequent
actions, for example opening the list of databases, tables or stored procedu
res on the object browser.
All my queries take ages to get going even for the simplest queries.
Previously the response was very reasonable, as are the other developers PCs
in the company, with similar set up.
I have tried using both forms of security but have no joy either way. I have
used the IP address – no go.
If I ping the NetBIOS name of the server the response is instantaneous.
Please help!!Did you remember to install SQL Server 2000 SP3a after the reinstall?
Without it, you are vulnerable to the Slammer.
Hope this helps.
Dan Guzman
SQL Server MVP
"Herbert Schroder" <herberts@.mweb.co.za> wrote in message
news:9FF54BCC-2F28-4F5A-9D6A-06A4D4B1CA41@.microsoft.com...
> Hi
> I have recently reinstalled XP Professional as well as the MSSQL client
tools.
> Our SQL 2000 server is running Win2K with 512MB RAM, and has been doing so
for quite a while, no changes where done to the server while I reinstalled
XP on my PC.
> Now my connection to the SQL server is extremely sluggish, e.g. connecting
via the Query Analyzer takes up to 2 minutes, and so do any other subsequent
actions, for example opening the list of databases, tables or stored
procedures on the object browser.
> All my queries take ages to get going even for the simplest queries.
> Previously the response was very reasonable, as are the other developers
PCs in the company, with similar set up.
> I have tried using both forms of security but have no joy either way. I
have used the IP address - no go.
> If I ping the NetBIOS name of the server the response is instantaneous.
>
> Please help!!
>

Extremely Slow connection time

Hi
I have recently reinstalled XP Professional as well as the MSSQL client tools.
Our SQL 2000 server is running Win2K with 512MB RAM, and has been doing so for quite a while, no changes where done to the server while I reinstalled XP on my PC.
Now my connection to the SQL server is extremely sluggish, e.g. connecting via the Query Analyzer takes up to 2 minutes, and so do any other subsequent actions, for example opening the list of databases, tables or stored procedures on the object browser.
All my queries take ages to get going even for the simplest queries.
Previously the response was very reasonable, as are the other developers PCs in the company, with similar set up.
I have tried using both forms of security but have no joy either way. I have used the IP address – no go.
If I ping the NetBIOS name of the server the response is instantaneous.
Please help!!
Did you remember to install SQL Server 2000 SP3a after the reinstall?
Without it, you are vulnerable to the Slammer.
Hope this helps.
Dan Guzman
SQL Server MVP
"Herbert Schroder" <herberts@.mweb.co.za> wrote in message
news:9FF54BCC-2F28-4F5A-9D6A-06A4D4B1CA41@.microsoft.com...
> Hi
> I have recently reinstalled XP Professional as well as the MSSQL client
tools.
> Our SQL 2000 server is running Win2K with 512MB RAM, and has been doing so
for quite a while, no changes where done to the server while I reinstalled
XP on my PC.
> Now my connection to the SQL server is extremely sluggish, e.g. connecting
via the Query Analyzer takes up to 2 minutes, and so do any other subsequent
actions, for example opening the list of databases, tables or stored
procedures on the object browser.
> All my queries take ages to get going even for the simplest queries.
> Previously the response was very reasonable, as are the other developers
PCs in the company, with similar set up.
> I have tried using both forms of security but have no joy either way. I
have used the IP address - no go.
> If I ping the NetBIOS name of the server the response is instantaneous.
>
> Please help!!
>