Hi all,
I have a database I maintain that has grown quite large. The part of it
I am interested in, is one paticular table that logs the history of
certain high volume "events". I have events back to 2002, and the
database is almost 3 Gigs. I rarely need to query more than 6 months
worth. Here is what I would like to do.
I'd like to split the database, and create an archive database. I want
to move everything before 2006 to this new database. Now, I know I can
do a complete backup, and then delete the stuff I don't need, but I
wanted to know if there is a way to import just the dates I need from
the current database. Of course, there is a timedate field to key off
of.
I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
2003 Server.
Thanks in advance.Hi there
There are several ways to do this. You can try to use DTS to move the data
over. Or you can use query analyzer. If you can use Query Analyzer, you can
actually use a query something like:
SELECT *
INTO [ArchiveDBName].dbo.[TableName]
FROM dbo.[OriginalDBName]
WHERE [DateStamp] < '1/1/2006'
And to delete the records from the original table:
DELETE FROM dbo.[OriginalDBName]
WHERE [DateStamp] < '1/1/2006'
However, it was not clear from you post if you have access to Query Analyzer
.
Lucas
"mattdaddym@.gmail.com" wrote:
> Hi all,
> I have a database I maintain that has grown quite large. The part of it
> I am interested in, is one paticular table that logs the history of
> certain high volume "events". I have events back to 2002, and the
> database is almost 3 Gigs. I rarely need to query more than 6 months
> worth. Here is what I would like to do.
> I'd like to split the database, and create an archive database. I want
> to move everything before 2006 to this new database. Now, I know I can
> do a complete backup, and then delete the stuff I don't need, but I
> wanted to know if there is a way to import just the dates I need from
> the current database. Of course, there is a timedate field to key off
> of.
> I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
> 2003 Server.
> Thanks in advance.
>|||I do have access to query analyzer. I was hoping for a way to do it in
the GUI since it creats the tables automatically when you do an import.
I don't know for sure, but I will assume if I use your command that I
will need to set the table up first. Not a big deal, though. I guess
I'm just being lazy. Thank you!
Lucas Kartawidjaja wrote:[vbcol=seagreen]
> Hi there
> There are several ways to do this. You can try to use DTS to move the data
> over. Or you can use query analyzer. If you can use Query Analyzer, you ca
n
> actually use a query something like:
> SELECT *
> INTO [ArchiveDBName].dbo.[TableName]
> FROM dbo.[OriginalDBName]
> WHERE [DateStamp] < '1/1/2006'
> And to delete the records from the original table:
> DELETE FROM dbo.[OriginalDBName]
> WHERE [DateStamp] < '1/1/2006'
> However, it was not clear from you post if you have access to Query Analyz
er.
> Lucas
>
> "mattdaddym@.gmail.com" wrote:
>|||Actually with the SELECT INTO statement the beauty of it is that you don't
need to create the table first. SELECT INTO will create it for you the table
structure will be the same as the original table.
Lucas
"mattdaddym@.gmail.com" wrote:
> I do have access to query analyzer. I was hoping for a way to do it in
> the GUI since it creats the tables automatically when you do an import.
> I don't know for sure, but I will assume if I use your command that I
> will need to set the table up first. Not a big deal, though. I guess
> I'm just being lazy. Thank you!
> Lucas Kartawidjaja wrote:
>|||That is great. Thank you!
Lucas Kartawidjaja wrote:[vbcol=seagreen]
> Actually with the SELECT INTO statement the beauty of it is that you don't
> need to create the table first. SELECT INTO will create it for you the tab
le
> structure will be the same as the original table.
> Lucas
> "mattdaddym@.gmail.com" wrote:
>
Showing posts with label history. Show all posts
Showing posts with label history. Show all posts
Thursday, March 29, 2012
database import question
Hi all,
I have a database I maintain that has grown quite large. The part of it
I am interested in, is one paticular table that logs the history of
certain high volume "events". I have events back to 2002, and the
database is almost 3 Gigs. I rarely need to query more than 6 months
worth. Here is what I would like to do.
I'd like to split the database, and create an archive database. I want
to move everything before 2006 to this new database. Now, I know I can
do a complete backup, and then delete the stuff I don't need, but I
wanted to know if there is a way to import just the dates I need from
the current database. Of course, there is a timedate field to key off
of.
I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
2003 Server.
Thanks in advance.Hi there
There are several ways to do this. You can try to use DTS to move the data
over. Or you can use query analyzer. If you can use Query Analyzer, you can
actually use a query something like:
SELECT *
INTO [ArchiveDBName].dbo.[TableName]
FROM dbo.[OriginalDBName]
WHERE [DateStamp] < '1/1/2006'
And to delete the records from the original table:
DELETE FROM dbo.[OriginalDBName]
WHERE [DateStamp] < '1/1/2006'
However, it was not clear from you post if you have access to Query Analyzer.
Lucas
"mattdaddym@.gmail.com" wrote:
> Hi all,
> I have a database I maintain that has grown quite large. The part of it
> I am interested in, is one paticular table that logs the history of
> certain high volume "events". I have events back to 2002, and the
> database is almost 3 Gigs. I rarely need to query more than 6 months
> worth. Here is what I would like to do.
> I'd like to split the database, and create an archive database. I want
> to move everything before 2006 to this new database. Now, I know I can
> do a complete backup, and then delete the stuff I don't need, but I
> wanted to know if there is a way to import just the dates I need from
> the current database. Of course, there is a timedate field to key off
> of.
> I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
> 2003 Server.
> Thanks in advance.
>|||I do have access to query analyzer. I was hoping for a way to do it in
the GUI since it creats the tables automatically when you do an import.
I don't know for sure, but I will assume if I use your command that I
will need to set the table up first. Not a big deal, though. I guess
I'm just being lazy. Thank you!
Lucas Kartawidjaja wrote:
> Hi there
> There are several ways to do this. You can try to use DTS to move the data
> over. Or you can use query analyzer. If you can use Query Analyzer, you can
> actually use a query something like:
> SELECT *
> INTO [ArchiveDBName].dbo.[TableName]
> FROM dbo.[OriginalDBName]
> WHERE [DateStamp] < '1/1/2006'
> And to delete the records from the original table:
> DELETE FROM dbo.[OriginalDBName]
> WHERE [DateStamp] < '1/1/2006'
> However, it was not clear from you post if you have access to Query Analyzer.
> Lucas
>
> "mattdaddym@.gmail.com" wrote:
> > Hi all,
> >
> > I have a database I maintain that has grown quite large. The part of it
> > I am interested in, is one paticular table that logs the history of
> > certain high volume "events". I have events back to 2002, and the
> > database is almost 3 Gigs. I rarely need to query more than 6 months
> > worth. Here is what I would like to do.
> >
> > I'd like to split the database, and create an archive database. I want
> > to move everything before 2006 to this new database. Now, I know I can
> > do a complete backup, and then delete the stuff I don't need, but I
> > wanted to know if there is a way to import just the dates I need from
> > the current database. Of course, there is a timedate field to key off
> > of.
> >
> > I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
> > 2003 Server.
> >
> > Thanks in advance.
> >
> >|||Actually with the SELECT INTO statement the beauty of it is that you don't
need to create the table first. SELECT INTO will create it for you the table
structure will be the same as the original table.
Lucas
"mattdaddym@.gmail.com" wrote:
> I do have access to query analyzer. I was hoping for a way to do it in
> the GUI since it creats the tables automatically when you do an import.
> I don't know for sure, but I will assume if I use your command that I
> will need to set the table up first. Not a big deal, though. I guess
> I'm just being lazy. Thank you!
> Lucas Kartawidjaja wrote:
> > Hi there
> >
> > There are several ways to do this. You can try to use DTS to move the data
> > over. Or you can use query analyzer. If you can use Query Analyzer, you can
> > actually use a query something like:
> >
> > SELECT *
> > INTO [ArchiveDBName].dbo.[TableName]
> > FROM dbo.[OriginalDBName]
> > WHERE [DateStamp] < '1/1/2006'
> >
> > And to delete the records from the original table:
> >
> > DELETE FROM dbo.[OriginalDBName]
> > WHERE [DateStamp] < '1/1/2006'
> >
> > However, it was not clear from you post if you have access to Query Analyzer.
> >
> > Lucas
> >
> >
> > "mattdaddym@.gmail.com" wrote:
> >
> > > Hi all,
> > >
> > > I have a database I maintain that has grown quite large. The part of it
> > > I am interested in, is one paticular table that logs the history of
> > > certain high volume "events". I have events back to 2002, and the
> > > database is almost 3 Gigs. I rarely need to query more than 6 months
> > > worth. Here is what I would like to do.
> > >
> > > I'd like to split the database, and create an archive database. I want
> > > to move everything before 2006 to this new database. Now, I know I can
> > > do a complete backup, and then delete the stuff I don't need, but I
> > > wanted to know if there is a way to import just the dates I need from
> > > the current database. Of course, there is a timedate field to key off
> > > of.
> > >
> > > I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
> > > 2003 Server.
> > >
> > > Thanks in advance.
> > >
> > >
>|||That is great. Thank you!
Lucas Kartawidjaja wrote:
> Actually with the SELECT INTO statement the beauty of it is that you don't
> need to create the table first. SELECT INTO will create it for you the table
> structure will be the same as the original table.
> Lucas
> "mattdaddym@.gmail.com" wrote:
> > I do have access to query analyzer. I was hoping for a way to do it in
> > the GUI since it creats the tables automatically when you do an import.
> > I don't know for sure, but I will assume if I use your command that I
> > will need to set the table up first. Not a big deal, though. I guess
> > I'm just being lazy. Thank you!
> > Lucas Kartawidjaja wrote:
> > > Hi there
> > >
> > > There are several ways to do this. You can try to use DTS to move the data
> > > over. Or you can use query analyzer. If you can use Query Analyzer, you can
> > > actually use a query something like:
> > >
> > > SELECT *
> > > INTO [ArchiveDBName].dbo.[TableName]
> > > FROM dbo.[OriginalDBName]
> > > WHERE [DateStamp] < '1/1/2006'
> > >
> > > And to delete the records from the original table:
> > >
> > > DELETE FROM dbo.[OriginalDBName]
> > > WHERE [DateStamp] < '1/1/2006'
> > >
> > > However, it was not clear from you post if you have access to Query Analyzer.
> > >
> > > Lucas
> > >
> > >
> > > "mattdaddym@.gmail.com" wrote:
> > >
> > > > Hi all,
> > > >
> > > > I have a database I maintain that has grown quite large. The part of it
> > > > I am interested in, is one paticular table that logs the history of
> > > > certain high volume "events". I have events back to 2002, and the
> > > > database is almost 3 Gigs. I rarely need to query more than 6 months
> > > > worth. Here is what I would like to do.
> > > >
> > > > I'd like to split the database, and create an archive database. I want
> > > > to move everything before 2006 to this new database. Now, I know I can
> > > > do a complete backup, and then delete the stuff I don't need, but I
> > > > wanted to know if there is a way to import just the dates I need from
> > > > the current database. Of course, there is a timedate field to key off
> > > > of.
> > > >
> > > > I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
> > > > 2003 Server.
> > > >
> > > > Thanks in advance.
> > > >
> > > >
> >
> >
I have a database I maintain that has grown quite large. The part of it
I am interested in, is one paticular table that logs the history of
certain high volume "events". I have events back to 2002, and the
database is almost 3 Gigs. I rarely need to query more than 6 months
worth. Here is what I would like to do.
I'd like to split the database, and create an archive database. I want
to move everything before 2006 to this new database. Now, I know I can
do a complete backup, and then delete the stuff I don't need, but I
wanted to know if there is a way to import just the dates I need from
the current database. Of course, there is a timedate field to key off
of.
I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
2003 Server.
Thanks in advance.Hi there
There are several ways to do this. You can try to use DTS to move the data
over. Or you can use query analyzer. If you can use Query Analyzer, you can
actually use a query something like:
SELECT *
INTO [ArchiveDBName].dbo.[TableName]
FROM dbo.[OriginalDBName]
WHERE [DateStamp] < '1/1/2006'
And to delete the records from the original table:
DELETE FROM dbo.[OriginalDBName]
WHERE [DateStamp] < '1/1/2006'
However, it was not clear from you post if you have access to Query Analyzer.
Lucas
"mattdaddym@.gmail.com" wrote:
> Hi all,
> I have a database I maintain that has grown quite large. The part of it
> I am interested in, is one paticular table that logs the history of
> certain high volume "events". I have events back to 2002, and the
> database is almost 3 Gigs. I rarely need to query more than 6 months
> worth. Here is what I would like to do.
> I'd like to split the database, and create an archive database. I want
> to move everything before 2006 to this new database. Now, I know I can
> do a complete backup, and then delete the stuff I don't need, but I
> wanted to know if there is a way to import just the dates I need from
> the current database. Of course, there is a timedate field to key off
> of.
> I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
> 2003 Server.
> Thanks in advance.
>|||I do have access to query analyzer. I was hoping for a way to do it in
the GUI since it creats the tables automatically when you do an import.
I don't know for sure, but I will assume if I use your command that I
will need to set the table up first. Not a big deal, though. I guess
I'm just being lazy. Thank you!
Lucas Kartawidjaja wrote:
> Hi there
> There are several ways to do this. You can try to use DTS to move the data
> over. Or you can use query analyzer. If you can use Query Analyzer, you can
> actually use a query something like:
> SELECT *
> INTO [ArchiveDBName].dbo.[TableName]
> FROM dbo.[OriginalDBName]
> WHERE [DateStamp] < '1/1/2006'
> And to delete the records from the original table:
> DELETE FROM dbo.[OriginalDBName]
> WHERE [DateStamp] < '1/1/2006'
> However, it was not clear from you post if you have access to Query Analyzer.
> Lucas
>
> "mattdaddym@.gmail.com" wrote:
> > Hi all,
> >
> > I have a database I maintain that has grown quite large. The part of it
> > I am interested in, is one paticular table that logs the history of
> > certain high volume "events". I have events back to 2002, and the
> > database is almost 3 Gigs. I rarely need to query more than 6 months
> > worth. Here is what I would like to do.
> >
> > I'd like to split the database, and create an archive database. I want
> > to move everything before 2006 to this new database. Now, I know I can
> > do a complete backup, and then delete the stuff I don't need, but I
> > wanted to know if there is a way to import just the dates I need from
> > the current database. Of course, there is a timedate field to key off
> > of.
> >
> > I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
> > 2003 Server.
> >
> > Thanks in advance.
> >
> >|||Actually with the SELECT INTO statement the beauty of it is that you don't
need to create the table first. SELECT INTO will create it for you the table
structure will be the same as the original table.
Lucas
"mattdaddym@.gmail.com" wrote:
> I do have access to query analyzer. I was hoping for a way to do it in
> the GUI since it creats the tables automatically when you do an import.
> I don't know for sure, but I will assume if I use your command that I
> will need to set the table up first. Not a big deal, though. I guess
> I'm just being lazy. Thank you!
> Lucas Kartawidjaja wrote:
> > Hi there
> >
> > There are several ways to do this. You can try to use DTS to move the data
> > over. Or you can use query analyzer. If you can use Query Analyzer, you can
> > actually use a query something like:
> >
> > SELECT *
> > INTO [ArchiveDBName].dbo.[TableName]
> > FROM dbo.[OriginalDBName]
> > WHERE [DateStamp] < '1/1/2006'
> >
> > And to delete the records from the original table:
> >
> > DELETE FROM dbo.[OriginalDBName]
> > WHERE [DateStamp] < '1/1/2006'
> >
> > However, it was not clear from you post if you have access to Query Analyzer.
> >
> > Lucas
> >
> >
> > "mattdaddym@.gmail.com" wrote:
> >
> > > Hi all,
> > >
> > > I have a database I maintain that has grown quite large. The part of it
> > > I am interested in, is one paticular table that logs the history of
> > > certain high volume "events". I have events back to 2002, and the
> > > database is almost 3 Gigs. I rarely need to query more than 6 months
> > > worth. Here is what I would like to do.
> > >
> > > I'd like to split the database, and create an archive database. I want
> > > to move everything before 2006 to this new database. Now, I know I can
> > > do a complete backup, and then delete the stuff I don't need, but I
> > > wanted to know if there is a way to import just the dates I need from
> > > the current database. Of course, there is a timedate field to key off
> > > of.
> > >
> > > I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
> > > 2003 Server.
> > >
> > > Thanks in advance.
> > >
> > >
>|||That is great. Thank you!
Lucas Kartawidjaja wrote:
> Actually with the SELECT INTO statement the beauty of it is that you don't
> need to create the table first. SELECT INTO will create it for you the table
> structure will be the same as the original table.
> Lucas
> "mattdaddym@.gmail.com" wrote:
> > I do have access to query analyzer. I was hoping for a way to do it in
> > the GUI since it creats the tables automatically when you do an import.
> > I don't know for sure, but I will assume if I use your command that I
> > will need to set the table up first. Not a big deal, though. I guess
> > I'm just being lazy. Thank you!
> > Lucas Kartawidjaja wrote:
> > > Hi there
> > >
> > > There are several ways to do this. You can try to use DTS to move the data
> > > over. Or you can use query analyzer. If you can use Query Analyzer, you can
> > > actually use a query something like:
> > >
> > > SELECT *
> > > INTO [ArchiveDBName].dbo.[TableName]
> > > FROM dbo.[OriginalDBName]
> > > WHERE [DateStamp] < '1/1/2006'
> > >
> > > And to delete the records from the original table:
> > >
> > > DELETE FROM dbo.[OriginalDBName]
> > > WHERE [DateStamp] < '1/1/2006'
> > >
> > > However, it was not clear from you post if you have access to Query Analyzer.
> > >
> > > Lucas
> > >
> > >
> > > "mattdaddym@.gmail.com" wrote:
> > >
> > > > Hi all,
> > > >
> > > > I have a database I maintain that has grown quite large. The part of it
> > > > I am interested in, is one paticular table that logs the history of
> > > > certain high volume "events". I have events back to 2002, and the
> > > > database is almost 3 Gigs. I rarely need to query more than 6 months
> > > > worth. Here is what I would like to do.
> > > >
> > > > I'd like to split the database, and create an archive database. I want
> > > > to move everything before 2006 to this new database. Now, I know I can
> > > > do a complete backup, and then delete the stuff I don't need, but I
> > > > wanted to know if there is a way to import just the dates I need from
> > > > the current database. Of course, there is a timedate field to key off
> > > > of.
> > > >
> > > > I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
> > > > 2003 Server.
> > > >
> > > > Thanks in advance.
> > > >
> > > >
> >
> >
Tuesday, March 27, 2012
Database History Info
Is there a way in SQL Server to check when the database was deleted?
Lito D
I would say most likely not. The files are deleted and the entry is removed
from sysdatabases.
However...
In msdb you can check the backup history. Table msdb.dbo.backupset holds
the records of all backups. If a database was dropped without deleting the
backup history (and the database was being backed up!) then you can find
when the last backup happened and infer the deletion date from that.
RLF
"LITO" <anynomous@.msn.com> wrote in message
news:F1C14E2A-6781-4C5E-818F-CDA3D19B30B4@.microsoft.com...
> Is there a way in SQL Server to check when the database was deleted?
> --
> Lito D
Lito D
I would say most likely not. The files are deleted and the entry is removed
from sysdatabases.
However...
In msdb you can check the backup history. Table msdb.dbo.backupset holds
the records of all backups. If a database was dropped without deleting the
backup history (and the database was being backed up!) then you can find
when the last backup happened and infer the deletion date from that.
RLF
"LITO" <anynomous@.msn.com> wrote in message
news:F1C14E2A-6781-4C5E-818F-CDA3D19B30B4@.microsoft.com...
> Is there a way in SQL Server to check when the database was deleted?
> --
> Lito D
Database History Info
Is there a way in SQL Server to check when the database was deleted?
--
Lito DI would say most likely not. The files are deleted and the entry is removed
from sysdatabases.
However...
In msdb you can check the backup history. Table msdb.dbo.backupset holds
the records of all backups. If a database was dropped without deleting the
backup history (and the database was being backed up!) then you can find
when the last backup happened and infer the deletion date from that.
RLF
"LITO" <anynomous@.msn.com> wrote in message
news:F1C14E2A-6781-4C5E-818F-CDA3D19B30B4@.microsoft.com...
> Is there a way in SQL Server to check when the database was deleted?
> --
> Lito D
--
Lito DI would say most likely not. The files are deleted and the entry is removed
from sysdatabases.
However...
In msdb you can check the backup history. Table msdb.dbo.backupset holds
the records of all backups. If a database was dropped without deleting the
backup history (and the database was being backed up!) then you can find
when the last backup happened and infer the deletion date from that.
RLF
"LITO" <anynomous@.msn.com> wrote in message
news:F1C14E2A-6781-4C5E-818F-CDA3D19B30B4@.microsoft.com...
> Is there a way in SQL Server to check when the database was deleted?
> --
> Lito D
Database History Info
Is there a way in SQL Server to check when the database was deleted?
--
Lito DI would say most likely not. The files are deleted and the entry is removed
from sysdatabases.
However...
In msdb you can check the backup history. Table msdb.dbo.backupset holds
the records of all backups. If a database was dropped without deleting the
backup history (and the database was being backed up!) then you can find
when the last backup happened and infer the deletion date from that.
RLF
"LITO" <anynomous@.msn.com> wrote in message
news:F1C14E2A-6781-4C5E-818F-CDA3D19B30B4@.microsoft.com...
> Is there a way in SQL Server to check when the database was deleted?
> --
> Lito D
--
Lito DI would say most likely not. The files are deleted and the entry is removed
from sysdatabases.
However...
In msdb you can check the backup history. Table msdb.dbo.backupset holds
the records of all backups. If a database was dropped without deleting the
backup history (and the database was being backed up!) then you can find
when the last backup happened and infer the deletion date from that.
RLF
"LITO" <anynomous@.msn.com> wrote in message
news:F1C14E2A-6781-4C5E-818F-CDA3D19B30B4@.microsoft.com...
> Is there a way in SQL Server to check when the database was deleted?
> --
> Lito D
Tuesday, February 14, 2012
Database Corruption?
Hi,
I have a 36GB database that has failed it's integrity checks as part of a
scheduled maintenance plan over the weekend. The plan history and job step
history did not provide any useful information. I've been trying to run a
DBCC CHECKDB on the database (no options) for the last 2 hours and it is
still running. In the past I believe the DBCC CHECKDB statement required
less than 30 minutes to complete. What are my options at this point outside
of restoring from a backup?
Thanks
Jerry
Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
recommendations?
Thanks
Jerry
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
> Hi,
> I have a 36GB database that has failed it's integrity checks as part of a
> scheduled maintenance plan over the weekend. The plan history and job
> step history did not provide any useful information. I've been trying to
> run a DBCC CHECKDB on the database (no options) for the last 2 hours and
> it is still running. In the past I believe the DBCC CHECKDB statement
> required less than 30 minutes to complete. What are my options at this
> point outside of restoring from a backup?
> Thanks
> Jerry
>
|||Hi
Rather wait the DBCC out and see what it shows. You rather find out now than
in another 24 hours that the DB is corrupt.
In the mean time, fine the last good backup and restore it to another server
to see if it is also corrupt and if you can actually restore 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/
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
> recommendations?
> Thanks
> Jerry
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
>
|||Thanks Mike. I was just starting that process as well as examining the
event logs to see if this could be a HW issue.
Will keep you posted.
Jerry
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
> Hi
> Rather wait the DBCC out and see what it shows. You rather find out now
> than in another 24 hours that the DB is corrupt.
> In the mean time, fine the last good backup and restore it to another
> server to see if it is also corrupt and if you can actually restore 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/
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
>
|||Ok...event log shows a SQL Server Assertion error and a Error 3624 from a
couple of days ago. Also, an Error 8648 "Index entry for row ID was not
found in index ID 2 of table 1403152044. However, a SELECT OBJECT_NAME with
this number reveals a stored procedure. Any ideas? The DBCC is still
running and the last backup should be on the test box in about 30 minutes.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:u1PqWzVvFHA.3500@.TK2MSFTNGP09.phx.gbl...
> Thanks Mike. I was just starting that process as well as examining the
> event logs to see if this could be a HW issue.
> Will keep you posted.
> Jerry
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
>
|||Problem solved. Corrupt NC index on table with apx 150 million rows.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:eaOzlIWvFHA.3720@.TK2MSFTNGP14.phx.gbl...
> Ok...event log shows a SQL Server Assertion error and a Error 3624 from a
> couple of days ago. Also, an Error 8648 "Index entry for row ID was not
> found in index ID 2 of table 1403152044. However, a SELECT OBJECT_NAME
> with this number reveals a stored procedure. Any ideas? The DBCC is
> still running and the last backup should be on the test box in about 30
> minutes.
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:u1PqWzVvFHA.3500@.TK2MSFTNGP09.phx.gbl...
>
|||FWIW, the extra time you're seeing comes from DBCC doing extensive
non-clustered index to base table cross checks to determine which NC index
rows have no matching data rows, or which data rows have no matching NC
index rows. This only happens when we find corruptions in the database,
and, as you have found, is quite time-consuming.
Thanks,
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:u0kgwaXvFHA.1256@.TK2MSFTNGP09.phx.gbl...
> Problem solved. Corrupt NC index on table with apx 150 million rows.
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:eaOzlIWvFHA.3720@.TK2MSFTNGP14.phx.gbl...
>
I have a 36GB database that has failed it's integrity checks as part of a
scheduled maintenance plan over the weekend. The plan history and job step
history did not provide any useful information. I've been trying to run a
DBCC CHECKDB on the database (no options) for the last 2 hours and it is
still running. In the past I believe the DBCC CHECKDB statement required
less than 30 minutes to complete. What are my options at this point outside
of restoring from a backup?
Thanks
Jerry
Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
recommendations?
Thanks
Jerry
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
> Hi,
> I have a 36GB database that has failed it's integrity checks as part of a
> scheduled maintenance plan over the weekend. The plan history and job
> step history did not provide any useful information. I've been trying to
> run a DBCC CHECKDB on the database (no options) for the last 2 hours and
> it is still running. In the past I believe the DBCC CHECKDB statement
> required less than 30 minutes to complete. What are my options at this
> point outside of restoring from a backup?
> Thanks
> Jerry
>
|||Hi
Rather wait the DBCC out and see what it shows. You rather find out now than
in another 24 hours that the DB is corrupt.
In the mean time, fine the last good backup and restore it to another server
to see if it is also corrupt and if you can actually restore 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/
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
> recommendations?
> Thanks
> Jerry
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
>
|||Thanks Mike. I was just starting that process as well as examining the
event logs to see if this could be a HW issue.
Will keep you posted.
Jerry
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
> Hi
> Rather wait the DBCC out and see what it shows. You rather find out now
> than in another 24 hours that the DB is corrupt.
> In the mean time, fine the last good backup and restore it to another
> server to see if it is also corrupt and if you can actually restore 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/
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
>
|||Ok...event log shows a SQL Server Assertion error and a Error 3624 from a
couple of days ago. Also, an Error 8648 "Index entry for row ID was not
found in index ID 2 of table 1403152044. However, a SELECT OBJECT_NAME with
this number reveals a stored procedure. Any ideas? The DBCC is still
running and the last backup should be on the test box in about 30 minutes.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:u1PqWzVvFHA.3500@.TK2MSFTNGP09.phx.gbl...
> Thanks Mike. I was just starting that process as well as examining the
> event logs to see if this could be a HW issue.
> Will keep you posted.
> Jerry
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
>
|||Problem solved. Corrupt NC index on table with apx 150 million rows.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:eaOzlIWvFHA.3720@.TK2MSFTNGP14.phx.gbl...
> Ok...event log shows a SQL Server Assertion error and a Error 3624 from a
> couple of days ago. Also, an Error 8648 "Index entry for row ID was not
> found in index ID 2 of table 1403152044. However, a SELECT OBJECT_NAME
> with this number reveals a stored procedure. Any ideas? The DBCC is
> still running and the last backup should be on the test box in about 30
> minutes.
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:u1PqWzVvFHA.3500@.TK2MSFTNGP09.phx.gbl...
>
|||FWIW, the extra time you're seeing comes from DBCC doing extensive
non-clustered index to base table cross checks to determine which NC index
rows have no matching data rows, or which data rows have no matching NC
index rows. This only happens when we find corruptions in the database,
and, as you have found, is quite time-consuming.
Thanks,
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:u0kgwaXvFHA.1256@.TK2MSFTNGP09.phx.gbl...
> Problem solved. Corrupt NC index on table with apx 150 million rows.
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:eaOzlIWvFHA.3720@.TK2MSFTNGP14.phx.gbl...
>
Database Corruption?
Hi,
I have a 36GB database that has failed it's integrity checks as part of a
scheduled maintenance plan over the weekend. The plan history and job step
history did not provide any useful information. I've been trying to run a
DBCC CHECKDB on the database (no options) for the last 2 hours and it is
still running. In the past I believe the DBCC CHECKDB statement required
less than 30 minutes to complete. What are my options at this point outside
of restoring from a backup?
Thanks
JerryOk...over 3 hours for the DBCC CHECKDB and it is still running. Any
recommendations?
Thanks
Jerry
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
> Hi,
> I have a 36GB database that has failed it's integrity checks as part of a
> scheduled maintenance plan over the weekend. The plan history and job
> step history did not provide any useful information. I've been trying to
> run a DBCC CHECKDB on the database (no options) for the last 2 hours and
> it is still running. In the past I believe the DBCC CHECKDB statement
> required less than 30 minutes to complete. What are my options at this
> point outside of restoring from a backup?
> Thanks
> Jerry
>|||Hi
Rather wait the DBCC out and see what it shows. You rather find out now than
in another 24 hours that the DB is corrupt.
In the mean time, fine the last good backup and restore it to another server
to see if it is also corrupt and if you can actually restore 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/
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
> recommendations?
> Thanks
> Jerry
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
>|||Thanks Mike. I was just starting that process as well as examining the
event logs to see if this could be a HW issue.
Will keep you posted.
Jerry
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
> Hi
> Rather wait the DBCC out and see what it shows. You rather find out now
> than in another 24 hours that the DB is corrupt.
> In the mean time, fine the last good backup and restore it to another
> server to see if it is also corrupt and if you can actually restore 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/
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
>|||Ok...event log shows a SQL Server Assertion error and a Error 3624 from a
couple of days ago. Also, an Error 8648 "Index entry for row ID was not
found in index ID 2 of table 1403152044. However, a SELECT OBJECT_NAME with
this number reveals a stored procedure. Any ideas? The DBCC is still
running and the last backup should be on the test box in about 30 minutes.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:u1PqWzVvFHA.3500@.TK2MSFTNGP09.phx.gbl...
> Thanks Mike. I was just starting that process as well as examining the
> event logs to see if this could be a HW issue.
> Will keep you posted.
> Jerry
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
>|||Problem solved. Corrupt NC index on table with apx 150 million rows.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:eaOzlIWvFHA.3720@.TK2MSFTNGP14.phx.gbl...
> Ok...event log shows a SQL Server Assertion error and a Error 3624 from a
> couple of days ago. Also, an Error 8648 "Index entry for row ID was not
> found in index ID 2 of table 1403152044. However, a SELECT OBJECT_NAME
> with this number reveals a stored procedure. Any ideas? The DBCC is
> still running and the last backup should be on the test box in about 30
> minutes.
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:u1PqWzVvFHA.3500@.TK2MSFTNGP09.phx.gbl...
>|||FWIW, the extra time you're seeing comes from DBCC doing extensive
non-clustered index to base table cross checks to determine which NC index
rows have no matching data rows, or which data rows have no matching NC
index rows. This only happens when we find corruptions in the database,
and, as you have found, is quite time-consuming.
Thanks,
--
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:u0kgwaXvFHA.1256@.TK2MSFTNGP09.phx.gbl...
> Problem solved. Corrupt NC index on table with apx 150 million rows.
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:eaOzlIWvFHA.3720@.TK2MSFTNGP14.phx.gbl...
>
I have a 36GB database that has failed it's integrity checks as part of a
scheduled maintenance plan over the weekend. The plan history and job step
history did not provide any useful information. I've been trying to run a
DBCC CHECKDB on the database (no options) for the last 2 hours and it is
still running. In the past I believe the DBCC CHECKDB statement required
less than 30 minutes to complete. What are my options at this point outside
of restoring from a backup?
Thanks
JerryOk...over 3 hours for the DBCC CHECKDB and it is still running. Any
recommendations?
Thanks
Jerry
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
> Hi,
> I have a 36GB database that has failed it's integrity checks as part of a
> scheduled maintenance plan over the weekend. The plan history and job
> step history did not provide any useful information. I've been trying to
> run a DBCC CHECKDB on the database (no options) for the last 2 hours and
> it is still running. In the past I believe the DBCC CHECKDB statement
> required less than 30 minutes to complete. What are my options at this
> point outside of restoring from a backup?
> Thanks
> Jerry
>|||Hi
Rather wait the DBCC out and see what it shows. You rather find out now than
in another 24 hours that the DB is corrupt.
In the mean time, fine the last good backup and restore it to another server
to see if it is also corrupt and if you can actually restore 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/
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
> recommendations?
> Thanks
> Jerry
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
>|||Thanks Mike. I was just starting that process as well as examining the
event logs to see if this could be a HW issue.
Will keep you posted.
Jerry
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
> Hi
> Rather wait the DBCC out and see what it shows. You rather find out now
> than in another 24 hours that the DB is corrupt.
> In the mean time, fine the last good backup and restore it to another
> server to see if it is also corrupt and if you can actually restore 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/
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
>|||Ok...event log shows a SQL Server Assertion error and a Error 3624 from a
couple of days ago. Also, an Error 8648 "Index entry for row ID was not
found in index ID 2 of table 1403152044. However, a SELECT OBJECT_NAME with
this number reveals a stored procedure. Any ideas? The DBCC is still
running and the last backup should be on the test box in about 30 minutes.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:u1PqWzVvFHA.3500@.TK2MSFTNGP09.phx.gbl...
> Thanks Mike. I was just starting that process as well as examining the
> event logs to see if this could be a HW issue.
> Will keep you posted.
> Jerry
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
>|||Problem solved. Corrupt NC index on table with apx 150 million rows.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:eaOzlIWvFHA.3720@.TK2MSFTNGP14.phx.gbl...
> Ok...event log shows a SQL Server Assertion error and a Error 3624 from a
> couple of days ago. Also, an Error 8648 "Index entry for row ID was not
> found in index ID 2 of table 1403152044. However, a SELECT OBJECT_NAME
> with this number reveals a stored procedure. Any ideas? The DBCC is
> still running and the last backup should be on the test box in about 30
> minutes.
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:u1PqWzVvFHA.3500@.TK2MSFTNGP09.phx.gbl...
>|||FWIW, the extra time you're seeing comes from DBCC doing extensive
non-clustered index to base table cross checks to determine which NC index
rows have no matching data rows, or which data rows have no matching NC
index rows. This only happens when we find corruptions in the database,
and, as you have found, is quite time-consuming.
Thanks,
--
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:u0kgwaXvFHA.1256@.TK2MSFTNGP09.phx.gbl...
> Problem solved. Corrupt NC index on table with apx 150 million rows.
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:eaOzlIWvFHA.3720@.TK2MSFTNGP14.phx.gbl...
>
Database Corruption?
Hi,
I have a 36GB database that has failed it's integrity checks as part of a
scheduled maintenance plan over the weekend. The plan history and job step
history did not provide any useful information. I've been trying to run a
DBCC CHECKDB on the database (no options) for the last 2 hours and it is
still running. In the past I believe the DBCC CHECKDB statement required
less than 30 minutes to complete. What are my options at this point outside
of restoring from a backup?
Thanks
JerryOk...over 3 hours for the DBCC CHECKDB and it is still running. Any
recommendations?
Thanks
Jerry
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
> Hi,
> I have a 36GB database that has failed it's integrity checks as part of a
> scheduled maintenance plan over the weekend. The plan history and job
> step history did not provide any useful information. I've been trying to
> run a DBCC CHECKDB on the database (no options) for the last 2 hours and
> it is still running. In the past I believe the DBCC CHECKDB statement
> required less than 30 minutes to complete. What are my options at this
> point outside of restoring from a backup?
> Thanks
> Jerry
>|||Hi
Rather wait the DBCC out and see what it shows. You rather find out now than
in another 24 hours that the DB is corrupt.
In the mean time, fine the last good backup and restore it to another server
to see if it is also corrupt and if you can actually restore 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/
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
> recommendations?
> Thanks
> Jerry
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
>> Hi,
>> I have a 36GB database that has failed it's integrity checks as part of a
>> scheduled maintenance plan over the weekend. The plan history and job
>> step history did not provide any useful information. I've been trying to
>> run a DBCC CHECKDB on the database (no options) for the last 2 hours and
>> it is still running. In the past I believe the DBCC CHECKDB statement
>> required less than 30 minutes to complete. What are my options at this
>> point outside of restoring from a backup?
>> Thanks
>> Jerry
>|||Thanks Mike. I was just starting that process as well as examining the
event logs to see if this could be a HW issue.
Will keep you posted.
Jerry
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
> Hi
> Rather wait the DBCC out and see what it shows. You rather find out now
> than in another 24 hours that the DB is corrupt.
> In the mean time, fine the last good backup and restore it to another
> server to see if it is also corrupt and if you can actually restore 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/
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
>> recommendations?
>> Thanks
>> Jerry
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
>> Hi,
>> I have a 36GB database that has failed it's integrity checks as part of
>> a scheduled maintenance plan over the weekend. The plan history and job
>> step history did not provide any useful information. I've been trying
>> to run a DBCC CHECKDB on the database (no options) for the last 2 hours
>> and it is still running. In the past I believe the DBCC CHECKDB
>> statement required less than 30 minutes to complete. What are my
>> options at this point outside of restoring from a backup?
>> Thanks
>> Jerry
>>
>|||Ok...event log shows a SQL Server Assertion error and a Error 3624 from a
couple of days ago. Also, an Error 8648 "Index entry for row ID was not
found in index ID 2 of table 1403152044. However, a SELECT OBJECT_NAME with
this number reveals a stored procedure. Any ideas? The DBCC is still
running and the last backup should be on the test box in about 30 minutes.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:u1PqWzVvFHA.3500@.TK2MSFTNGP09.phx.gbl...
> Thanks Mike. I was just starting that process as well as examining the
> event logs to see if this could be a HW issue.
> Will keep you posted.
> Jerry
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
>> Hi
>> Rather wait the DBCC out and see what it shows. You rather find out now
>> than in another 24 hours that the DB is corrupt.
>> In the mean time, fine the last good backup and restore it to another
>> server to see if it is also corrupt and if you can actually restore 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/
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
>> recommendations?
>> Thanks
>> Jerry
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
>> Hi,
>> I have a 36GB database that has failed it's integrity checks as part of
>> a scheduled maintenance plan over the weekend. The plan history and
>> job step history did not provide any useful information. I've been
>> trying to run a DBCC CHECKDB on the database (no options) for the last
>> 2 hours and it is still running. In the past I believe the DBCC
>> CHECKDB statement required less than 30 minutes to complete. What are
>> my options at this point outside of restoring from a backup?
>> Thanks
>> Jerry
>>
>>
>|||Problem solved. Corrupt NC index on table with apx 150 million rows.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:eaOzlIWvFHA.3720@.TK2MSFTNGP14.phx.gbl...
> Ok...event log shows a SQL Server Assertion error and a Error 3624 from a
> couple of days ago. Also, an Error 8648 "Index entry for row ID was not
> found in index ID 2 of table 1403152044. However, a SELECT OBJECT_NAME
> with this number reveals a stored procedure. Any ideas? The DBCC is
> still running and the last backup should be on the test box in about 30
> minutes.
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:u1PqWzVvFHA.3500@.TK2MSFTNGP09.phx.gbl...
>> Thanks Mike. I was just starting that process as well as examining the
>> event logs to see if this could be a HW issue.
>> Will keep you posted.
>> Jerry
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
>> Hi
>> Rather wait the DBCC out and see what it shows. You rather find out now
>> than in another 24 hours that the DB is corrupt.
>> In the mean time, fine the last good backup and restore it to another
>> server to see if it is also corrupt and if you can actually restore 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/
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
>> recommendations?
>> Thanks
>> Jerry
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
>> Hi,
>> I have a 36GB database that has failed it's integrity checks as part
>> of a scheduled maintenance plan over the weekend. The plan history
>> and job step history did not provide any useful information. I've
>> been trying to run a DBCC CHECKDB on the database (no options) for the
>> last 2 hours and it is still running. In the past I believe the DBCC
>> CHECKDB statement required less than 30 minutes to complete. What are
>> my options at this point outside of restoring from a backup?
>> Thanks
>> Jerry
>>
>>
>>
>|||FWIW, the extra time you're seeing comes from DBCC doing extensive
non-clustered index to base table cross checks to determine which NC index
rows have no matching data rows, or which data rows have no matching NC
index rows. This only happens when we find corruptions in the database,
and, as you have found, is quite time-consuming.
Thanks,
--
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:u0kgwaXvFHA.1256@.TK2MSFTNGP09.phx.gbl...
> Problem solved. Corrupt NC index on table with apx 150 million rows.
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:eaOzlIWvFHA.3720@.TK2MSFTNGP14.phx.gbl...
>> Ok...event log shows a SQL Server Assertion error and a Error 3624 from a
>> couple of days ago. Also, an Error 8648 "Index entry for row ID was not
>> found in index ID 2 of table 1403152044. However, a SELECT OBJECT_NAME
>> with this number reveals a stored procedure. Any ideas? The DBCC is
>> still running and the last backup should be on the test box in about 30
>> minutes.
>>
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:u1PqWzVvFHA.3500@.TK2MSFTNGP09.phx.gbl...
>> Thanks Mike. I was just starting that process as well as examining the
>> event logs to see if this could be a HW issue.
>> Will keep you posted.
>> Jerry
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
>> Hi
>> Rather wait the DBCC out and see what it shows. You rather find out now
>> than in another 24 hours that the DB is corrupt.
>> In the mean time, fine the last good backup and restore it to another
>> server to see if it is also corrupt and if you can actually restore 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/
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
>> recommendations?
>> Thanks
>> Jerry
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
>> Hi,
>> I have a 36GB database that has failed it's integrity checks as part
>> of a scheduled maintenance plan over the weekend. The plan history
>> and job step history did not provide any useful information. I've
>> been trying to run a DBCC CHECKDB on the database (no options) for
>> the last 2 hours and it is still running. In the past I believe the
>> DBCC CHECKDB statement required less than 30 minutes to complete.
>> What are my options at this point outside of restoring from a backup?
>> Thanks
>> Jerry
>>
>>
>>
>>
>
I have a 36GB database that has failed it's integrity checks as part of a
scheduled maintenance plan over the weekend. The plan history and job step
history did not provide any useful information. I've been trying to run a
DBCC CHECKDB on the database (no options) for the last 2 hours and it is
still running. In the past I believe the DBCC CHECKDB statement required
less than 30 minutes to complete. What are my options at this point outside
of restoring from a backup?
Thanks
JerryOk...over 3 hours for the DBCC CHECKDB and it is still running. Any
recommendations?
Thanks
Jerry
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
> Hi,
> I have a 36GB database that has failed it's integrity checks as part of a
> scheduled maintenance plan over the weekend. The plan history and job
> step history did not provide any useful information. I've been trying to
> run a DBCC CHECKDB on the database (no options) for the last 2 hours and
> it is still running. In the past I believe the DBCC CHECKDB statement
> required less than 30 minutes to complete. What are my options at this
> point outside of restoring from a backup?
> Thanks
> Jerry
>|||Hi
Rather wait the DBCC out and see what it shows. You rather find out now than
in another 24 hours that the DB is corrupt.
In the mean time, fine the last good backup and restore it to another server
to see if it is also corrupt and if you can actually restore 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/
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
> recommendations?
> Thanks
> Jerry
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
>> Hi,
>> I have a 36GB database that has failed it's integrity checks as part of a
>> scheduled maintenance plan over the weekend. The plan history and job
>> step history did not provide any useful information. I've been trying to
>> run a DBCC CHECKDB on the database (no options) for the last 2 hours and
>> it is still running. In the past I believe the DBCC CHECKDB statement
>> required less than 30 minutes to complete. What are my options at this
>> point outside of restoring from a backup?
>> Thanks
>> Jerry
>|||Thanks Mike. I was just starting that process as well as examining the
event logs to see if this could be a HW issue.
Will keep you posted.
Jerry
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
> Hi
> Rather wait the DBCC out and see what it shows. You rather find out now
> than in another 24 hours that the DB is corrupt.
> In the mean time, fine the last good backup and restore it to another
> server to see if it is also corrupt and if you can actually restore 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/
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
>> recommendations?
>> Thanks
>> Jerry
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
>> Hi,
>> I have a 36GB database that has failed it's integrity checks as part of
>> a scheduled maintenance plan over the weekend. The plan history and job
>> step history did not provide any useful information. I've been trying
>> to run a DBCC CHECKDB on the database (no options) for the last 2 hours
>> and it is still running. In the past I believe the DBCC CHECKDB
>> statement required less than 30 minutes to complete. What are my
>> options at this point outside of restoring from a backup?
>> Thanks
>> Jerry
>>
>|||Ok...event log shows a SQL Server Assertion error and a Error 3624 from a
couple of days ago. Also, an Error 8648 "Index entry for row ID was not
found in index ID 2 of table 1403152044. However, a SELECT OBJECT_NAME with
this number reveals a stored procedure. Any ideas? The DBCC is still
running and the last backup should be on the test box in about 30 minutes.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:u1PqWzVvFHA.3500@.TK2MSFTNGP09.phx.gbl...
> Thanks Mike. I was just starting that process as well as examining the
> event logs to see if this could be a HW issue.
> Will keep you posted.
> Jerry
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
>> Hi
>> Rather wait the DBCC out and see what it shows. You rather find out now
>> than in another 24 hours that the DB is corrupt.
>> In the mean time, fine the last good backup and restore it to another
>> server to see if it is also corrupt and if you can actually restore 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/
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
>> recommendations?
>> Thanks
>> Jerry
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
>> Hi,
>> I have a 36GB database that has failed it's integrity checks as part of
>> a scheduled maintenance plan over the weekend. The plan history and
>> job step history did not provide any useful information. I've been
>> trying to run a DBCC CHECKDB on the database (no options) for the last
>> 2 hours and it is still running. In the past I believe the DBCC
>> CHECKDB statement required less than 30 minutes to complete. What are
>> my options at this point outside of restoring from a backup?
>> Thanks
>> Jerry
>>
>>
>|||Problem solved. Corrupt NC index on table with apx 150 million rows.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:eaOzlIWvFHA.3720@.TK2MSFTNGP14.phx.gbl...
> Ok...event log shows a SQL Server Assertion error and a Error 3624 from a
> couple of days ago. Also, an Error 8648 "Index entry for row ID was not
> found in index ID 2 of table 1403152044. However, a SELECT OBJECT_NAME
> with this number reveals a stored procedure. Any ideas? The DBCC is
> still running and the last backup should be on the test box in about 30
> minutes.
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:u1PqWzVvFHA.3500@.TK2MSFTNGP09.phx.gbl...
>> Thanks Mike. I was just starting that process as well as examining the
>> event logs to see if this could be a HW issue.
>> Will keep you posted.
>> Jerry
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
>> Hi
>> Rather wait the DBCC out and see what it shows. You rather find out now
>> than in another 24 hours that the DB is corrupt.
>> In the mean time, fine the last good backup and restore it to another
>> server to see if it is also corrupt and if you can actually restore 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/
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
>> recommendations?
>> Thanks
>> Jerry
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
>> Hi,
>> I have a 36GB database that has failed it's integrity checks as part
>> of a scheduled maintenance plan over the weekend. The plan history
>> and job step history did not provide any useful information. I've
>> been trying to run a DBCC CHECKDB on the database (no options) for the
>> last 2 hours and it is still running. In the past I believe the DBCC
>> CHECKDB statement required less than 30 minutes to complete. What are
>> my options at this point outside of restoring from a backup?
>> Thanks
>> Jerry
>>
>>
>>
>|||FWIW, the extra time you're seeing comes from DBCC doing extensive
non-clustered index to base table cross checks to determine which NC index
rows have no matching data rows, or which data rows have no matching NC
index rows. This only happens when we find corruptions in the database,
and, as you have found, is quite time-consuming.
Thanks,
--
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:u0kgwaXvFHA.1256@.TK2MSFTNGP09.phx.gbl...
> Problem solved. Corrupt NC index on table with apx 150 million rows.
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:eaOzlIWvFHA.3720@.TK2MSFTNGP14.phx.gbl...
>> Ok...event log shows a SQL Server Assertion error and a Error 3624 from a
>> couple of days ago. Also, an Error 8648 "Index entry for row ID was not
>> found in index ID 2 of table 1403152044. However, a SELECT OBJECT_NAME
>> with this number reveals a stored procedure. Any ideas? The DBCC is
>> still running and the last backup should be on the test box in about 30
>> minutes.
>>
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:u1PqWzVvFHA.3500@.TK2MSFTNGP09.phx.gbl...
>> Thanks Mike. I was just starting that process as well as examining the
>> event logs to see if this could be a HW issue.
>> Will keep you posted.
>> Jerry
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:uj25DxVvFHA.3792@.TK2MSFTNGP10.phx.gbl...
>> Hi
>> Rather wait the DBCC out and see what it shows. You rather find out now
>> than in another 24 hours that the DB is corrupt.
>> In the mean time, fine the last good backup and restore it to another
>> server to see if it is also corrupt and if you can actually restore 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/
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:%23UswseVvFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Ok...over 3 hours for the DBCC CHECKDB and it is still running. Any
>> recommendations?
>> Thanks
>> Jerry
>> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> news:%23j6KB$UvFHA.2504@.tk2msftngp13.phx.gbl...
>> Hi,
>> I have a 36GB database that has failed it's integrity checks as part
>> of a scheduled maintenance plan over the weekend. The plan history
>> and job step history did not provide any useful information. I've
>> been trying to run a DBCC CHECKDB on the database (no options) for
>> the last 2 hours and it is still running. In the past I believe the
>> DBCC CHECKDB statement required less than 30 minutes to complete.
>> What are my options at this point outside of restoring from a backup?
>> Thanks
>> Jerry
>>
>>
>>
>>
>
Subscribe to:
Posts (Atom)