We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
Advanced Server.
Weekly we have a job that drops all indexes on the database and recreates
them.
This job runs at the same time the daily backup and transaction log execute.
We received following error caused by the re-index:
"Time out occurred while waiting for buffer latch type 4..."
Please help me resolve these latch errors.
Thanks,
SQL Server errorlog
WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
continuing to wait.
Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0.
It not good practice to run such major maintenance operations as dropping
and recreating all indexes (I hope you use DBCC DBREINDEX btw) at the same
time as a backup. In general running the operations in parallel will not be
much quicker than running them in series (because your resources, specially
disk I/O, are limited). And if your backup finishes before the reindexing
finishes, part of your indexes will be reindexed and part not, but you don't
know exactly which.
Jacco Schalkwijk
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:AA424678-958D-478E-B6FF-574A7885455B@.microsoft.com...
> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log
> execute.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC
> 0x962263F0.
>
>
|||Hi
What does select @.@.version return for the SQL Server?
Have a look at:
http://support.microsoft.com/kb/310834/en-us
http://support.microsoft.com/kb/309093/EN-US/
Regards
Mike
"Joe K." wrote:
> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log execute.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0.
>
>
Showing posts with label enterprise. Show all posts
Showing posts with label enterprise. Show all posts
Friday, March 30, 2012
Not a BUF latch. Error Re-Indexing
We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
Advanced Server.
Weekly we have a job that drops all indexes on the database and recreates
them.
This job runs at the same time the daily backup and transaction log execute.
We received following error caused by the re-index:
"Time out occurred while waiting for buffer latch type 4..."
Please help me resolve these latch errors.
Thanks,
SQL Server errorlog
WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
continuing to wait.
Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0.It not good practice to run such major maintenance operations as dropping
and recreating all indexes (I hope you use DBCC DBREINDEX btw) at the same
time as a backup. In general running the operations in parallel will not be
much quicker than running them in series (because your resources, specially
disk I/O, are limited). And if your backup finishes before the reindexing
finishes, part of your indexes will be reindexed and part not, but you don't
know exactly which.
--
Jacco Schalkwijk
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:AA424678-958D-478E-B6FF-574A7885455B@.microsoft.com...
> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log
> execute.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC
> 0x962263F0.
>
>|||Hi
What does select @.@.version return for the SQL Server?
Have a look at:
http://support.microsoft.com/kb/310834/en-us
http://support.microsoft.com/kb/309093/EN-US/
Regards
Mike
"Joe K." wrote:
> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log execute.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0.
>
>
Advanced Server.
Weekly we have a job that drops all indexes on the database and recreates
them.
This job runs at the same time the daily backup and transaction log execute.
We received following error caused by the re-index:
"Time out occurred while waiting for buffer latch type 4..."
Please help me resolve these latch errors.
Thanks,
SQL Server errorlog
WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
continuing to wait.
Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0.It not good practice to run such major maintenance operations as dropping
and recreating all indexes (I hope you use DBCC DBREINDEX btw) at the same
time as a backup. In general running the operations in parallel will not be
much quicker than running them in series (because your resources, specially
disk I/O, are limited). And if your backup finishes before the reindexing
finishes, part of your indexes will be reindexed and part not, but you don't
know exactly which.
--
Jacco Schalkwijk
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:AA424678-958D-478E-B6FF-574A7885455B@.microsoft.com...
> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log
> execute.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC
> 0x962263F0.
>
>|||Hi
What does select @.@.version return for the SQL Server?
Have a look at:
http://support.microsoft.com/kb/310834/en-us
http://support.microsoft.com/kb/309093/EN-US/
Regards
Mike
"Joe K." wrote:
> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log execute.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0.
>
>
Not a BUF latch. Error Re-Indexing
We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
Advanced Server.
Weekly we have a job that drops all indexes on the database and recreates
them.
This job runs at the same time the daily backup and transaction log execute.
We received following error caused by the re-index:
"Time out occurred while waiting for buffer latch type 4..."
Please help me resolve these latch errors.
Thanks,
SQL Server errorlog
WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
continuing to wait.
Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0.It not good practice to run such major maintenance operations as dropping
and recreating all indexes (I hope you use DBCC DBREINDEX btw) at the same
time as a backup. In general running the operations in parallel will not be
much quicker than running them in series (because your resources, specially
disk I/O, are limited). And if your backup finishes before the reindexing
finishes, part of your indexes will be reindexed and part not, but you don't
know exactly which.
Jacco Schalkwijk
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:AA424678-958D-478E-B6FF-574A7885455B@.microsoft.com...
> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log
> execute.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC
> 0x962263F0.
>
>|||Hi
What does select @.@.version return for the SQL Server?
Have a look at:
http://support.microsoft.com/kb/310834/en-us
http://support.microsoft.com/kb/309093/EN-US/
Regards
Mike
"Joe K." wrote:
> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log execut
e.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0
.
>
>
Advanced Server.
Weekly we have a job that drops all indexes on the database and recreates
them.
This job runs at the same time the daily backup and transaction log execute.
We received following error caused by the re-index:
"Time out occurred while waiting for buffer latch type 4..."
Please help me resolve these latch errors.
Thanks,
SQL Server errorlog
WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
continuing to wait.
Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0.It not good practice to run such major maintenance operations as dropping
and recreating all indexes (I hope you use DBCC DBREINDEX btw) at the same
time as a backup. In general running the operations in parallel will not be
much quicker than running them in series (because your resources, specially
disk I/O, are limited). And if your backup finishes before the reindexing
finishes, part of your indexes will be reindexed and part not, but you don't
know exactly which.
Jacco Schalkwijk
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:AA424678-958D-478E-B6FF-574A7885455B@.microsoft.com...
> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log
> execute.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC
> 0x962263F0.
>
>|||Hi
What does select @.@.version return for the SQL Server?
Have a look at:
http://support.microsoft.com/kb/310834/en-us
http://support.microsoft.com/kb/309093/EN-US/
Regards
Mike
"Joe K." wrote:
> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log execut
e.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0
.
>
>
Monday, March 26, 2012
Noobie SQL question
I am getting this message when I try to open the database in the enterprise manager. In all other locations it is telling me that the database is running any thoughts on how to resolve this?
The SQL Server \\CRISPINDB1 is not known to be running. Are you sure you wish to connect?
Anything at all will be a great help to me thanks in advance.is \\CRISPINDB1 your machine or a server ?|||you've got to start SQL Server services|||\\CRISPINDB1 is the name of the machine and the services are running. The machines that need to access the database seem to not be having a problem getting to it and using it. Only when I try to access it thru Enterprise Manager.|||I am using the Enterprise manager on the machine that the database is running. Sorry about not giving all the info to know whats going on.|||maybe you need to add the instancename
\\ServerName\InstanceName|||With further investigation I have learned that patients are a virtue I was just trying to expand the tree before the application had polled he database. Thank you for your help on this operator caused problem. And with this I am a little less of a Noob about SQL.
The SQL Server \\CRISPINDB1 is not known to be running. Are you sure you wish to connect?
Anything at all will be a great help to me thanks in advance.is \\CRISPINDB1 your machine or a server ?|||you've got to start SQL Server services|||\\CRISPINDB1 is the name of the machine and the services are running. The machines that need to access the database seem to not be having a problem getting to it and using it. Only when I try to access it thru Enterprise Manager.|||I am using the Enterprise manager on the machine that the database is running. Sorry about not giving all the info to know whats going on.|||maybe you need to add the instancename
\\ServerName\InstanceName|||With further investigation I have learned that patients are a virtue I was just trying to expand the tree before the application had polled he database. Thank you for your help on this operator caused problem. And with this I am a little less of a Noob about SQL.
Monday, March 12, 2012
Non replicated tables and MS Access
What happens whey you try to edit the data in these
tables - any error messages etc? How are you editing
them - using Enterprise manager? (If so you must move off
the line for the edit to be committed).
Regards,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Hi Paul,
Manage to find the problem. An index was missing from the table which
prohibited MS Access from updating a row.
Howevere I was always able to edit a row using MS Query Analyser
Thanks
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:2b2201c49ee7$e565e230$a301280a@.phx.gbl...
> What happens whey you try to edit the data in these
> tables - any error messages etc? How are you editing
> them - using Enterprise manager? (If so you must move off
> the line for the edit to be committed).
> Regards,
> Paul Ibison
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
tables - any error messages etc? How are you editing
them - using Enterprise manager? (If so you must move off
the line for the edit to be committed).
Regards,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Hi Paul,
Manage to find the problem. An index was missing from the table which
prohibited MS Access from updating a row.
Howevere I was always able to edit a row using MS Query Analyser
Thanks
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:2b2201c49ee7$e565e230$a301280a@.phx.gbl...
> What happens whey you try to edit the data in these
> tables - any error messages etc? How are you editing
> them - using Enterprise manager? (If so you must move off
> the line for the edit to be committed).
> Regards,
> Paul Ibison
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
Friday, March 9, 2012
non clustered index
Can anyone tell me why Enterprise manager-Generate SQL
scripts utility does not generate scripts for non
clustered index? Thanks.
Because you didn't check "Script indexes" on the Options tab of the Generate
SQL Scripts dialog?
http://www.aspfaq.com/
(Reverse address to reply.)
"Bill" <fei0405@.yahoo.com> wrote in message
news:0e3801c49cf5$0493c450$a501280a@.phx.gbl...
> Can anyone tell me why Enterprise manager-Generate SQL
> scripts utility does not generate scripts for non
> clustered index? Thanks.
|||Or you missed it in the Alter Table section?
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ekeFnbPnEHA.3996@.TK2MSFTNGP09.phx.gbl...
> Because you didn't check "Script indexes" on the Options tab of the
Generate
> SQL Scripts dialog?
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Bill" <fei0405@.yahoo.com> wrote in message
> news:0e3801c49cf5$0493c450$a501280a@.phx.gbl...
>
|||Thank you. I did checked "Script indexes" on the Options
tab. I don't see Alter Table section. Can you navigate me
a little bit? Thank you so much.
>--Original Message--
>Or you missed it in the Alter Table section?
>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote
in message[vbcol=seagreen]
>news:ekeFnbPnEHA.3996@.TK2MSFTNGP09.phx.gbl...
Options tab of the
>Generate
>
>.
>
|||> Thank you. I did checked "Script indexes" on the Options
> tab.
Which index(es) are you expecting to get scripted? If they're the
system-generated ones (WA_SYS...) they won't be generated because these are
created by the system based on stats. If you're having a problem scripting
something you created, then show us how you created it and exactly what you
are doing that's failing.
|||Make sure you have a non-clustered index. The best would be create one.
Then check by right clicking the table, All Tasks, Manage Indexes, look at
whether there is one with clustered as no.
Then right click the table, all tasks, generate sql script, option tab,
check the script indexes box.
"Bill" <anonymous@.discussions.microsoft.com> wrote in message
news:1bae01c49cf8$e65243f0$a301280a@.phx.gbl...[vbcol=seagreen]
> Thank you. I did checked "Script indexes" on the Options
> tab. I don't see Alter Table section. Can you navigate me
> a little bit? Thank you so much.
> in message
> Options tab of the
|||Thank you very much.
Following the steps in your first paragraph, I only got
the scrip on one UNIQUE CLUSTERED index:
CREATE UNIQUE CLUSTERED
INDEX [PS_RF_ATTR_INSP] ON [dbo].[PS_RF_ATTR_INSP]
([SETID], [INST_PROD_ID], [MARKET], [ATTRIBUTE_ID])
WITH
FILLFACTOR = 90
,DROP_EXISTING
ON [PRIMARY]
When I issue command "sp_helpindex PS_RF_ATTR_INSP
go" I got more nonclustered index names as below:
index_name index_description
index_keys
PS_RF_ATTR_INSP clustered, unique located on PRIMARY
SETID, INST_PROD_ID, MARKET,ATTRIBUTE_ID
index_name index_description
index_keys
PS0RF_INST_PROD nonclustered located on PRIMARY
BO_ID_CUST, SETID, INST_PROD_ID
PS1RF_INST_PROD nonclustered located on PRIMARY
BO_ID_CONTACT, SETID, INST_PROD_ID
... ...
How could I get the scripts for those nonclustered indexes
for the table?
>--Original Message--
>Make sure you have a non-clustered index. The best would
be create one.
>Then check by right clicking the table, All Tasks, Manage
Indexes, look at
>whether there is one with clustered as no.
>Then right click the table, all tasks, generate sql
script, option tab,
>check the script indexes box.
>"Bill" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:1bae01c49cf8$e65243f0$a301280a@.phx.gbl...
me[vbcol=seagreen]
SQL
>
>.
>
scripts utility does not generate scripts for non
clustered index? Thanks.
Because you didn't check "Script indexes" on the Options tab of the Generate
SQL Scripts dialog?
http://www.aspfaq.com/
(Reverse address to reply.)
"Bill" <fei0405@.yahoo.com> wrote in message
news:0e3801c49cf5$0493c450$a501280a@.phx.gbl...
> Can anyone tell me why Enterprise manager-Generate SQL
> scripts utility does not generate scripts for non
> clustered index? Thanks.
|||Or you missed it in the Alter Table section?
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ekeFnbPnEHA.3996@.TK2MSFTNGP09.phx.gbl...
> Because you didn't check "Script indexes" on the Options tab of the
Generate
> SQL Scripts dialog?
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Bill" <fei0405@.yahoo.com> wrote in message
> news:0e3801c49cf5$0493c450$a501280a@.phx.gbl...
>
|||Thank you. I did checked "Script indexes" on the Options
tab. I don't see Alter Table section. Can you navigate me
a little bit? Thank you so much.
>--Original Message--
>Or you missed it in the Alter Table section?
>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote
in message[vbcol=seagreen]
>news:ekeFnbPnEHA.3996@.TK2MSFTNGP09.phx.gbl...
Options tab of the
>Generate
>
>.
>
|||> Thank you. I did checked "Script indexes" on the Options
> tab.
Which index(es) are you expecting to get scripted? If they're the
system-generated ones (WA_SYS...) they won't be generated because these are
created by the system based on stats. If you're having a problem scripting
something you created, then show us how you created it and exactly what you
are doing that's failing.
|||Make sure you have a non-clustered index. The best would be create one.
Then check by right clicking the table, All Tasks, Manage Indexes, look at
whether there is one with clustered as no.
Then right click the table, all tasks, generate sql script, option tab,
check the script indexes box.
"Bill" <anonymous@.discussions.microsoft.com> wrote in message
news:1bae01c49cf8$e65243f0$a301280a@.phx.gbl...[vbcol=seagreen]
> Thank you. I did checked "Script indexes" on the Options
> tab. I don't see Alter Table section. Can you navigate me
> a little bit? Thank you so much.
> in message
> Options tab of the
|||Thank you very much.
Following the steps in your first paragraph, I only got
the scrip on one UNIQUE CLUSTERED index:
CREATE UNIQUE CLUSTERED
INDEX [PS_RF_ATTR_INSP] ON [dbo].[PS_RF_ATTR_INSP]
([SETID], [INST_PROD_ID], [MARKET], [ATTRIBUTE_ID])
WITH
FILLFACTOR = 90
,DROP_EXISTING
ON [PRIMARY]
When I issue command "sp_helpindex PS_RF_ATTR_INSP
go" I got more nonclustered index names as below:
index_name index_description
index_keys
PS_RF_ATTR_INSP clustered, unique located on PRIMARY
SETID, INST_PROD_ID, MARKET,ATTRIBUTE_ID
index_name index_description
index_keys
PS0RF_INST_PROD nonclustered located on PRIMARY
BO_ID_CUST, SETID, INST_PROD_ID
PS1RF_INST_PROD nonclustered located on PRIMARY
BO_ID_CONTACT, SETID, INST_PROD_ID
... ...
How could I get the scripts for those nonclustered indexes
for the table?
>--Original Message--
>Make sure you have a non-clustered index. The best would
be create one.
>Then check by right clicking the table, All Tasks, Manage
Indexes, look at
>whether there is one with clustered as no.
>Then right click the table, all tasks, generate sql
script, option tab,
>check the script indexes box.
>"Bill" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:1bae01c49cf8$e65243f0$a301280a@.phx.gbl...
me[vbcol=seagreen]
SQL
>
>.
>
non clustered index
Can anyone tell me why Enterprise manager-Generate SQL
scripts utility does not generate scripts for non
clustered index? Thanks.Because you didn't check "Script indexes" on the Options tab of the Generate
SQL Scripts dialog?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Bill" <fei0405@.yahoo.com> wrote in message
news:0e3801c49cf5$0493c450$a501280a@.phx.gbl...
> Can anyone tell me why Enterprise manager-Generate SQL
> scripts utility does not generate scripts for non
> clustered index? Thanks.|||Or you missed it in the Alter Table section?
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ekeFnbPnEHA.3996@.TK2MSFTNGP09.phx.gbl...
> Because you didn't check "Script indexes" on the Options tab of the
Generate
> SQL Scripts dialog?
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Bill" <fei0405@.yahoo.com> wrote in message
> news:0e3801c49cf5$0493c450$a501280a@.phx.gbl...
> > Can anyone tell me why Enterprise manager-Generate SQL
> > scripts utility does not generate scripts for non
> > clustered index? Thanks.
>|||Thank you. I did checked "Script indexes" on the Options
tab. I don't see Alter Table section. Can you navigate me
a little bit? Thank you so much.
>--Original Message--
>Or you missed it in the Alter Table section?
>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote
in message
>news:ekeFnbPnEHA.3996@.TK2MSFTNGP09.phx.gbl...
>> Because you didn't check "Script indexes" on the
Options tab of the
>Generate
>> SQL Scripts dialog?
>> --
>> http://www.aspfaq.com/
>> (Reverse address to reply.)
>>
>>
>> "Bill" <fei0405@.yahoo.com> wrote in message
>> news:0e3801c49cf5$0493c450$a501280a@.phx.gbl...
>> > Can anyone tell me why Enterprise manager-Generate SQL
>> > scripts utility does not generate scripts for non
>> > clustered index? Thanks.
>>
>
>.
>|||> Thank you. I did checked "Script indexes" on the Options
> tab.
Which index(es) are you expecting to get scripted? If they're the
system-generated ones (WA_SYS...) they won't be generated because these are
created by the system based on stats. If you're having a problem scripting
something you created, then show us how you created it and exactly what you
are doing that's failing.|||Make sure you have a non-clustered index. The best would be create one.
Then check by right clicking the table, All Tasks, Manage Indexes, look at
whether there is one with clustered as no.
Then right click the table, all tasks, generate sql script, option tab,
check the script indexes box.
"Bill" <anonymous@.discussions.microsoft.com> wrote in message
news:1bae01c49cf8$e65243f0$a301280a@.phx.gbl...
> Thank you. I did checked "Script indexes" on the Options
> tab. I don't see Alter Table section. Can you navigate me
> a little bit? Thank you so much.
> >--Original Message--
> >Or you missed it in the Alter Table section?
> >
> >"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote
> in message
> >news:ekeFnbPnEHA.3996@.TK2MSFTNGP09.phx.gbl...
> >> Because you didn't check "Script indexes" on the
> Options tab of the
> >Generate
> >> SQL Scripts dialog?
> >>
> >> --
> >> http://www.aspfaq.com/
> >> (Reverse address to reply.)
> >>
> >>
> >>
> >>
> >> "Bill" <fei0405@.yahoo.com> wrote in message
> >> news:0e3801c49cf5$0493c450$a501280a@.phx.gbl...
> >> > Can anyone tell me why Enterprise manager-Generate SQL
> >> > scripts utility does not generate scripts for non
> >> > clustered index? Thanks.
> >>
> >>
> >
> >
> >.
> >|||Thank you very much.
Following the steps in your first paragraph, I only got
the scrip on one UNIQUE CLUSTERED index:
CREATE UNIQUE CLUSTERED
INDEX [PS_RF_ATTR_INSP] ON [dbo].[PS_RF_ATTR_INSP]
([SETID], [INST_PROD_ID], [MARKET], [ATTRIBUTE_ID])
WITH
FILLFACTOR = 90
,DROP_EXISTING
ON [PRIMARY]
When I issue command "sp_helpindex PS_RF_ATTR_INSP
go" I got more nonclustered index names as below:
index_name index_description
index_keys
PS_RF_ATTR_INSP clustered, unique located on PRIMARY
SETID, INST_PROD_ID, MARKET,ATTRIBUTE_ID
index_name index_description
index_keys
PS0RF_INST_PROD nonclustered located on PRIMARY
BO_ID_CUST, SETID, INST_PROD_ID
PS1RF_INST_PROD nonclustered located on PRIMARY
BO_ID_CONTACT, SETID, INST_PROD_ID
... ...
How could I get the scripts for those nonclustered indexes
for the table?
>--Original Message--
>Make sure you have a non-clustered index. The best would
be create one.
>Then check by right clicking the table, All Tasks, Manage
Indexes, look at
>whether there is one with clustered as no.
>Then right click the table, all tasks, generate sql
script, option tab,
>check the script indexes box.
>"Bill" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1bae01c49cf8$e65243f0$a301280a@.phx.gbl...
>> Thank you. I did checked "Script indexes" on the Options
>> tab. I don't see Alter Table section. Can you navigate
me
>> a little bit? Thank you so much.
>> >--Original Message--
>> >Or you missed it in the Alter Table section?
>> >
>> >"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote
>> in message
>> >news:ekeFnbPnEHA.3996@.TK2MSFTNGP09.phx.gbl...
>> >> Because you didn't check "Script indexes" on the
>> Options tab of the
>> >Generate
>> >> SQL Scripts dialog?
>> >>
>> >> --
>> >> http://www.aspfaq.com/
>> >> (Reverse address to reply.)
>> >>
>> >>
>> >>
>> >>
>> >> "Bill" <fei0405@.yahoo.com> wrote in message
>> >> news:0e3801c49cf5$0493c450$a501280a@.phx.gbl...
>> >> > Can anyone tell me why Enterprise manager-Generate
SQL
>> >> > scripts utility does not generate scripts for non
>> >> > clustered index? Thanks.
>> >>
>> >>
>> >
>> >
>> >.
>> >
>
>.
>
scripts utility does not generate scripts for non
clustered index? Thanks.Because you didn't check "Script indexes" on the Options tab of the Generate
SQL Scripts dialog?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Bill" <fei0405@.yahoo.com> wrote in message
news:0e3801c49cf5$0493c450$a501280a@.phx.gbl...
> Can anyone tell me why Enterprise manager-Generate SQL
> scripts utility does not generate scripts for non
> clustered index? Thanks.|||Or you missed it in the Alter Table section?
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ekeFnbPnEHA.3996@.TK2MSFTNGP09.phx.gbl...
> Because you didn't check "Script indexes" on the Options tab of the
Generate
> SQL Scripts dialog?
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Bill" <fei0405@.yahoo.com> wrote in message
> news:0e3801c49cf5$0493c450$a501280a@.phx.gbl...
> > Can anyone tell me why Enterprise manager-Generate SQL
> > scripts utility does not generate scripts for non
> > clustered index? Thanks.
>|||Thank you. I did checked "Script indexes" on the Options
tab. I don't see Alter Table section. Can you navigate me
a little bit? Thank you so much.
>--Original Message--
>Or you missed it in the Alter Table section?
>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote
in message
>news:ekeFnbPnEHA.3996@.TK2MSFTNGP09.phx.gbl...
>> Because you didn't check "Script indexes" on the
Options tab of the
>Generate
>> SQL Scripts dialog?
>> --
>> http://www.aspfaq.com/
>> (Reverse address to reply.)
>>
>>
>> "Bill" <fei0405@.yahoo.com> wrote in message
>> news:0e3801c49cf5$0493c450$a501280a@.phx.gbl...
>> > Can anyone tell me why Enterprise manager-Generate SQL
>> > scripts utility does not generate scripts for non
>> > clustered index? Thanks.
>>
>
>.
>|||> Thank you. I did checked "Script indexes" on the Options
> tab.
Which index(es) are you expecting to get scripted? If they're the
system-generated ones (WA_SYS...) they won't be generated because these are
created by the system based on stats. If you're having a problem scripting
something you created, then show us how you created it and exactly what you
are doing that's failing.|||Make sure you have a non-clustered index. The best would be create one.
Then check by right clicking the table, All Tasks, Manage Indexes, look at
whether there is one with clustered as no.
Then right click the table, all tasks, generate sql script, option tab,
check the script indexes box.
"Bill" <anonymous@.discussions.microsoft.com> wrote in message
news:1bae01c49cf8$e65243f0$a301280a@.phx.gbl...
> Thank you. I did checked "Script indexes" on the Options
> tab. I don't see Alter Table section. Can you navigate me
> a little bit? Thank you so much.
> >--Original Message--
> >Or you missed it in the Alter Table section?
> >
> >"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote
> in message
> >news:ekeFnbPnEHA.3996@.TK2MSFTNGP09.phx.gbl...
> >> Because you didn't check "Script indexes" on the
> Options tab of the
> >Generate
> >> SQL Scripts dialog?
> >>
> >> --
> >> http://www.aspfaq.com/
> >> (Reverse address to reply.)
> >>
> >>
> >>
> >>
> >> "Bill" <fei0405@.yahoo.com> wrote in message
> >> news:0e3801c49cf5$0493c450$a501280a@.phx.gbl...
> >> > Can anyone tell me why Enterprise manager-Generate SQL
> >> > scripts utility does not generate scripts for non
> >> > clustered index? Thanks.
> >>
> >>
> >
> >
> >.
> >|||Thank you very much.
Following the steps in your first paragraph, I only got
the scrip on one UNIQUE CLUSTERED index:
CREATE UNIQUE CLUSTERED
INDEX [PS_RF_ATTR_INSP] ON [dbo].[PS_RF_ATTR_INSP]
([SETID], [INST_PROD_ID], [MARKET], [ATTRIBUTE_ID])
WITH
FILLFACTOR = 90
,DROP_EXISTING
ON [PRIMARY]
When I issue command "sp_helpindex PS_RF_ATTR_INSP
go" I got more nonclustered index names as below:
index_name index_description
index_keys
PS_RF_ATTR_INSP clustered, unique located on PRIMARY
SETID, INST_PROD_ID, MARKET,ATTRIBUTE_ID
index_name index_description
index_keys
PS0RF_INST_PROD nonclustered located on PRIMARY
BO_ID_CUST, SETID, INST_PROD_ID
PS1RF_INST_PROD nonclustered located on PRIMARY
BO_ID_CONTACT, SETID, INST_PROD_ID
... ...
How could I get the scripts for those nonclustered indexes
for the table?
>--Original Message--
>Make sure you have a non-clustered index. The best would
be create one.
>Then check by right clicking the table, All Tasks, Manage
Indexes, look at
>whether there is one with clustered as no.
>Then right click the table, all tasks, generate sql
script, option tab,
>check the script indexes box.
>"Bill" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1bae01c49cf8$e65243f0$a301280a@.phx.gbl...
>> Thank you. I did checked "Script indexes" on the Options
>> tab. I don't see Alter Table section. Can you navigate
me
>> a little bit? Thank you so much.
>> >--Original Message--
>> >Or you missed it in the Alter Table section?
>> >
>> >"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote
>> in message
>> >news:ekeFnbPnEHA.3996@.TK2MSFTNGP09.phx.gbl...
>> >> Because you didn't check "Script indexes" on the
>> Options tab of the
>> >Generate
>> >> SQL Scripts dialog?
>> >>
>> >> --
>> >> http://www.aspfaq.com/
>> >> (Reverse address to reply.)
>> >>
>> >>
>> >>
>> >>
>> >> "Bill" <fei0405@.yahoo.com> wrote in message
>> >> news:0e3801c49cf5$0493c450$a501280a@.phx.gbl...
>> >> > Can anyone tell me why Enterprise manager-Generate
SQL
>> >> > scripts utility does not generate scripts for non
>> >> > clustered index? Thanks.
>> >>
>> >>
>> >
>> >
>> >.
>> >
>
>.
>
Monday, February 20, 2012
no sync replication instructions.
Hello.
Does anyone have instructions on how to set back up replication that has
been marked for re-initilization thru the gui (enterprise manager)? We
have a subscriber that had their wan link down for the whole weekend and
now all their publications are marked for reinitialization. Some the
tables in question are 20gb in size, and that is just too big for us to
re-do snapshots and send over a WAN link. So in reading Hilary's and
Pauls post it looks like a "no-sync" will help me not have to send over
a snap shot.
1. how do i do this through enterprise manager only?
2. is there anyway for me to tell replication to go back lets say the
last 48hrs for the tables that we replicate, and "repush" that data
over?
Thanks,
-comb
Comb,
this article should help:
http://www.replicationanswers.com/No...alizations.asp
Initially I'd use Redgate's DataCompare to sync the data for any stray
changes.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||In article <eo9dqUZrFHA.1256@.TK2MSFTNGP09.phx.gbl>,
Paul.Ibison@.Pygmalion.Com says...
> Comb,
> this article should help:
> http://www.replicationanswers.com/No...alizations.asp
> Initially I'd use Redgate's DataCompare to sync the data for any stray
> changes.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
Thanks Paul. I appreciate yours and hilary's help.
looking now. I am also going to look into this Redgates.
-comb
Does anyone have instructions on how to set back up replication that has
been marked for re-initilization thru the gui (enterprise manager)? We
have a subscriber that had their wan link down for the whole weekend and
now all their publications are marked for reinitialization. Some the
tables in question are 20gb in size, and that is just too big for us to
re-do snapshots and send over a WAN link. So in reading Hilary's and
Pauls post it looks like a "no-sync" will help me not have to send over
a snap shot.
1. how do i do this through enterprise manager only?
2. is there anyway for me to tell replication to go back lets say the
last 48hrs for the tables that we replicate, and "repush" that data
over?
Thanks,
-comb
Comb,
this article should help:
http://www.replicationanswers.com/No...alizations.asp
Initially I'd use Redgate's DataCompare to sync the data for any stray
changes.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||In article <eo9dqUZrFHA.1256@.TK2MSFTNGP09.phx.gbl>,
Paul.Ibison@.Pygmalion.Com says...
> Comb,
> this article should help:
> http://www.replicationanswers.com/No...alizations.asp
> Initially I'd use Redgate's DataCompare to sync the data for any stray
> changes.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
Thanks Paul. I appreciate yours and hilary's help.
looking now. I am also going to look into this Redgates.
-comb
Subscribe to:
Posts (Atom)