Backup failure Error Log Messages

I have not been able to find any details about backup failures for
MSSQL 2000. I am researching the following:
1. when a backup fails at a certain point during the process does the
backup:
A. stop there having recorded some details?
B. quit without backing up any of the data it already processed?
C. skip the data it cannot read and move on?
2. Does the error log record any of the details above? For instance, if
there is a table that the backup could not write to .bak, does the
error log report exactly where the error was?

I need a way to obtain a Backup Exception 'Report' that when a backup
fails it can tell me what did not get into the .bak file. I would
prefer automatic notification. Our Oracle DBs have something setup
that can be run when a piece of the DB does not get backed up letting
the Oracle DBA know where there are issues.

Thank you,
StephanieHi
1. B
2. If it is a write failure, yes it will be in the SQL Log. If it is data
corruption, it is in the SQL Log.

For a backup to fail, due to internal SQL Server problems is very very rare,
and I have not seen it on a clean database before.

Most failures are caused by running out of disk space or anti virus messing
around on the file when SQL is trying to write to it.

Regards
----------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@.epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"Stephanie" <stuttle@.centene.com> wrote in message
news:1123710578.824686.208370@.g47g2000cwa.googlegr oups.com...
>I have not been able to find any details about backup failures for
> MSSQL 2000. I am researching the following:
> 1. when a backup fails at a certain point during the process does the
> backup:
> A. stop there having recorded some details?
> B. quit without backing up any of the data it already processed?
> C. skip the data it cannot read and move on?
> 2. Does the error log record any of the details above? For instance, if
> there is a table that the backup could not write to .bak, does the
> error log report exactly where the error was?
> I need a way to obtain a Backup Exception 'Report' that when a backup
> fails it can tell me what did not get into the .bak file. I would
> prefer automatic notification. Our Oracle DBs have something setup
> that can be run when a piece of the DB does not get backed up letting
> the Oracle DBA know where there are issues.
> Thank you,
> Stephanie

Backing up tables

I use SQL Server 2000 and I create scripts on a daily basis to do the following

1. Rename a table
2. Create table with original name and add new field
3. Copy data from renamed table to new table
4. Build indexes
-------------
execute sp_rename ORIGINAL, OLD
GO

CREATE TABLE [dbo].[ORIGINAL] (
[A] [varchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
[B] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
[C] [int] NOT NULL ,
[Notes] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
GO

INSERT INTO ORIGINAL (A, B, NOTES)
SELECT A, B, NOTES
FROM OLD

CREATE CLUSTERED INDEX [ORIGINAL_A_B] ON [dbo].[ORIGINAL]([A], [B] DESC ) WITH FILLFACTOR = 90 ON [PRIMARY]
GO
-------------

ON A TABLE WITH 100,000 RECORDS THIS KIND OF SCRIPT TAKES A LONG TIME TO DO THE INSERT/SELECT PART

I WOULD USE ALTER/ADD TO UPDATE THE TABLES, BUT MY SUPERIOR INSISTS THAT NOT HAVING TEXT FIELDS AS THE LAST FIELD IN THE TABLE WILL CAUSE QUERKY PROBLEMS WITH HIS SQL STATEMENTS
DOES ANYONE HAVE ANY KNOWLEDGE THAT THIS COULD BE TRUE?

IF SO,
DOES ANYONE HAVE ANY IDEAS FOR DOING THIS SAME PROCESS TO ADD A NEW FIELD (C) BEFORE THE FINAL FIELD (NOTES - TEXT FIELD), AND BACKUP THE TABLE BUT WITHOUT IT TAKING SUCH A LONG TIME ON THE INSERT/SELECT PART?

Forgive me if I'm asking a lot, but I'm lost and these scripts take way too long for what seems like such a simple task.

Thanks,
MitchWow sounds like he has a DB2 OS/390 v2.3 background

Look up the datatype in BOL...

They store pointer values, not the data...it's stored separatley...

If you don't mind being fired, call him a scrub...

The order of columns in a table should have very little impact...

But being anal goes with the job...

Try a bcp out and in with a format file...

The reason it's slow is because it's all being logged...the bcp will log only the pages...not every row....|||EDIT:

Oh, and btw, I use ALTER