create index with drop existing

Create index with drop existing after succesfull creation,
when dbcc checktable is run, at times it does not finish
at all, when killed and again submitted runs okay.
Vinodh,
Are you saying that the dbcc does not finish or the create index? How long
did you wait? How big is the table, and how many indexes on there?
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
"Vinodh" <anonymous@.discussions.microsoft.com> wrote in message
news:b85901c437d6$ef3b81c0$a401280a@.phx.gbl...
> Create index with drop existing after succesfull creation,
> when dbcc checktable is run, at times it does not finish
> at all, when killed and again submitted runs okay.
>

create index with drop existing

Create index with drop existing after succesfull creation,
when dbcc checktable is run, at times it does not finish
at all, when killed and again submitted runs okay.Vinodh,
Are you saying that the dbcc does not finish or the create index? How long
did you wait? How big is the table, and how many indexes on there?
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
"Vinodh" <anonymous@.discussions.microsoft.com> wrote in message
news:b85901c437d6$ef3b81c0$a401280a@.phx.gbl...
> Create index with drop existing after succesfull creation,
> when dbcc checktable is run, at times it does not finish
> at all, when killed and again submitted runs okay.
>

create index with drop existing

Create index with drop existing after succesfull creation,
when dbcc checktable is run, at times it does not finish
at all, when killed and again submitted runs okay.Vinodh,
Are you saying that the dbcc does not finish or the create index? How long
did you wait? How big is the table, and how many indexes on there?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
"Vinodh" <anonymous@.discussions.microsoft.com> wrote in message
news:b85901c437d6$ef3b81c0$a401280a@.phx.gbl...
> Create index with drop existing after succesfull creation,
> when dbcc checktable is run, at times it does not finish
> at all, when killed and again submitted runs okay.
>

create corruption

Is there a way to create db corruption without deleting a row from
sysIndexes? That method still allows dbcc checkdb to return "CHECKDB found 0
allocation errors and 0 consistency errors in database bla" and I want it to
return an error.
TIA,
ChrisR
Ugh! I'm trying to get rid of it and you're trying to create it! ;-)
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:8CEFC956-B85C-4A1C-9AF4-D793C14FADB8@.microsoft.com...
> Is there a way to create db corruption without deleting a row from
> sysIndexes? That method still allows dbcc checkdb to return "CHECKDB found
> 0
> allocation errors and 0 consistency errors in database bla" and I want it
> to
> return an error.
> --
> TIA,
> ChrisR
|||Hi,
you could edit the .mdf file with a editor and enter some char's on the file.
I never done it but i think it could work : )
CC
"ChrisR" wrote:

> Is there a way to create db corruption without deleting a row from
> sysIndexes? That method still allows dbcc checkdb to return "CHECKDB found 0
> allocation errors and 0 consistency errors in database bla" and I want it to
> return an error.
> --
> TIA,
> ChrisR
|||That would leave it suspect, not corrupted. Thanks though.
TIA,
ChrisR
"CC" wrote:
[vbcol=seagreen]
> Hi,
> you could edit the .mdf file with a editor and enter some char's on the file.
> I never done it but i think it could work : )
> CC
> "ChrisR" wrote:
|||No - it would only leave it suspect if recovery runs across the page you
corrupted. Your best bet is to delete a row from sysindexes. Instead of the
script you posted in a previous thread, its far easier to create a single
non-clustered index, insert a few rows and then
delete * from sysindexes
where indid=2 and
id=object_id ('mytable')
You should get a variety of errors from CHECKDB.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:A16120B3-C62D-4355-A402-5F858AFEA293@.microsoft.com...[vbcol=seagreen]
> That would leave it suspect, not corrupted. Thanks though.
> --
> TIA,
> ChrisR
>
> "CC" wrote:

create corruption

Is there a way to create db corruption without deleting a row from
sysIndexes? That method still allows dbcc checkdb to return "CHECKDB found 0
allocation errors and 0 consistency errors in database bla" and I want it to
return an error.
--
TIA,
ChrisRUgh! I'm trying to get rid of it and you're trying to create it! ;-)
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:8CEFC956-B85C-4A1C-9AF4-D793C14FADB8@.microsoft.com...
> Is there a way to create db corruption without deleting a row from
> sysIndexes? That method still allows dbcc checkdb to return "CHECKDB found
> 0
> allocation errors and 0 consistency errors in database bla" and I want it
> to
> return an error.
> --
> TIA,
> ChrisR|||Hi,
you could edit the .mdf file with a editor and enter some char's on the file
.
I never done it but i think it could work : )
CC
"ChrisR" wrote:

> Is there a way to create db corruption without deleting a row from
> sysIndexes? That method still allows dbcc checkdb to return "CHECKDB found
0
> allocation errors and 0 consistency errors in database bla" and I want it
to
> return an error.
> --
> TIA,
> ChrisR|||That would leave it suspect, not corrupted. Thanks though.
--
TIA,
ChrisR
"CC" wrote:
[vbcol=seagreen]
> Hi,
> you could edit the .mdf file with a editor and enter some char's on the fi
le.
> I never done it but i think it could work : )
> CC
> "ChrisR" wrote:
>|||No - it would only leave it suspect if recovery runs across the page you
corrupted. Your best bet is to delete a row from sysindexes. Instead of the
script you posted in a previous thread, its far easier to create a single
non-clustered index, insert a few rows and then
delete * from sysindexes
where indid=2 and
id=object_id ('mytable')
You should get a variety of errors from CHECKDB.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:A16120B3-C62D-4355-A402-5F858AFEA293@.microsoft.com...[vbcol=seagreen]
> That would leave it suspect, not corrupted. Thanks though.
> --
> TIA,
> ChrisR
>
> "CC" wrote:
>

create corruption

Is there a way to create db corruption without deleting a row from
sysIndexes? That method still allows dbcc checkdb to return "CHECKDB found 0
allocation errors and 0 consistency errors in database bla" and I want it to
return an error.
--
TIA,
ChrisRUgh! I'm trying to get rid of it and you're trying to create it! ;-)
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:8CEFC956-B85C-4A1C-9AF4-D793C14FADB8@.microsoft.com...
> Is there a way to create db corruption without deleting a row from
> sysIndexes? That method still allows dbcc checkdb to return "CHECKDB found
> 0
> allocation errors and 0 consistency errors in database bla" and I want it
> to
> return an error.
> --
> TIA,
> ChrisR|||Hi,
you could edit the .mdf file with a editor and enter some char's on the file.
I never done it but i think it could work : )
CC
"ChrisR" wrote:
> Is there a way to create db corruption without deleting a row from
> sysIndexes? That method still allows dbcc checkdb to return "CHECKDB found 0
> allocation errors and 0 consistency errors in database bla" and I want it to
> return an error.
> --
> TIA,
> ChrisR|||That would leave it suspect, not corrupted. Thanks though.
--
TIA,
ChrisR
"CC" wrote:
> Hi,
> you could edit the .mdf file with a editor and enter some char's on the file.
> I never done it but i think it could work : )
> CC
> "ChrisR" wrote:
> > Is there a way to create db corruption without deleting a row from
> > sysIndexes? That method still allows dbcc checkdb to return "CHECKDB found 0
> > allocation errors and 0 consistency errors in database bla" and I want it to
> > return an error.
> > --
> > TIA,
> > ChrisR|||No - it would only leave it suspect if recovery runs across the page you
corrupted. Your best bet is to delete a row from sysindexes. Instead of the
script you posted in a previous thread, its far easier to create a single
non-clustered index, insert a few rows and then
delete * from sysindexes
where indid=2 and
id=object_id ('mytable')
You should get a variety of errors from CHECKDB.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:A16120B3-C62D-4355-A402-5F858AFEA293@.microsoft.com...
> That would leave it suspect, not corrupted. Thanks though.
> --
> TIA,
> ChrisR
>
> "CC" wrote:
>> Hi,
>> you could edit the .mdf file with a editor and enter some char's on the
>> file.
>> I never done it but i think it could work : )
>> CC
>> "ChrisR" wrote:
>> > Is there a way to create db corruption without deleting a row from
>> > sysIndexes? That method still allows dbcc checkdb to return "CHECKDB
>> > found 0
>> > allocation errors and 0 consistency errors in database bla" and I want
>> > it to
>> > return an error.
>> > --
>> > TIA,
>> > ChrisR