hi,
I need to shring a SQL 2000 db by 50GB. Is it better to start sql in single
user mode when doing such action?
I believe you will find that the database will be put into single user mode
for the life of your shrink session automatically. But it might simplify
matters to do it manually.
Joseph R.P. Maloney, CSP,CCP,CDP
"stoney" wrote:
> hi,
> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in single
> user mode when doing such action?
|||Thanks very much for your prompt response. Does the system have a better
performance if I shrink the database more often? Say if I shrink the
database every 3 months.
Thanks.
"jrpm" <jrpm@.discussions.microsoft.com> wrote in message
news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...[vbcol=seagreen]
>I believe you will find that the database will be put into single user mode
> for the life of your shrink session automatically. But it might simplify
> matters to do it manually.
>
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "stoney" wrote:
|||In my humble opinion database server perform better with their logs shrunk
and stored in medias.
The data are more important than the logs.
and logs are overhead to database services
thats why a sound backup and restore strategy must implemented
thanks,
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"Diane Walker" wrote:
> Thanks very much for your prompt response. Does the system have a better
> performance if I shrink the database more often? Say if I shrink the
> database every 3 months.
> Thanks.
> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>
>
|||Shrinking does not require the db to be in single user mode and there is
nothing that does that automatically.
Andrew J. Kelly SQL MVP
"jrpm" <jrpm@.discussions.microsoft.com> wrote in message
news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...[vbcol=seagreen]
>I believe you will find that the database will be put into single user mode
> for the life of your shrink session automatically. But it might simplify
> matters to do it manually.
>
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "stoney" wrote:
|||Actually you get better performance if you don't shrink it at all in most
cases. If you need to keep shrinking it that is a pretty good indication it
wants to be larger than you think it should be. So leave it alone. See
this:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Andrew J. Kelly SQL MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
> Thanks very much for your prompt response. Does the system have a better
> performance if I shrink the database more often? Say if I shrink the
> database every 3 months.
> Thanks.
> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>
|||Just the opposite. Transaction logs are crucial to performance on SQL
Server. Since all data manipulation is sent to the transaction log first it
will slow everything else down if it can not write fast enough. By
shrinking the log files too much you will force them to grow just when it
needs to write entries to the log file. They then must wait on that
operation to complete before they can continue.
Andrew J. Kelly SQL MVP
"Jose G. de Jesus Jr MCP, MCDBA" <Email me> wrote in message
news:986EDB0C-E8C8-47F5-8646-175E0CE40A22@.microsoft.com...[vbcol=seagreen]
> In my humble opinion database server perform better with their logs shrunk
> and stored in medias.
> The data are more important than the logs.
> and logs are overhead to database services
> thats why a sound backup and restore strategy must implemented
> --
> thanks,
> --
> Jose de Jesus Jr. Mcp,Mcdba
> Data Architect
> Sykes Asia (Manila philippines)
> MCP #2324787
>
> "Diane Walker" wrote:
|||Thanks very much for the information.
"Jose G. de Jesus Jr MCP, MCDBA" <Email me> wrote in message
news:986EDB0C-E8C8-47F5-8646-175E0CE40A22@.microsoft.com...[vbcol=seagreen]
> In my humble opinion database server perform better with their logs shrunk
> and stored in medias.
> The data are more important than the logs.
> and logs are overhead to database services
> thats why a sound backup and restore strategy must implemented
> --
> thanks,
> --
> Jose de Jesus Jr. Mcp,Mcdba
> Data Architect
> Sykes Asia (Manila philippines)
> MCP #2324787
>
> "Diane Walker" wrote:
|||My database file is 55 MB. The transaction log is 14 GB. Do you recommend
that I leave the transaction log alone? Thanks.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uKa26MFwFHA.2516@.TK2MSFTNGP12.phx.gbl...
> Actually you get better performance if you don't shrink it at all in most
> cases. If you need to keep shrinking it that is a pretty good indication
> it wants to be larger than you think it should be. So leave it alone.
> See this:
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> --
> Andrew J. Kelly SQL MVP
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
>
|||No that is excessive and warrants a shrinking<g>. But why did it get there
in the first place? Chances are you are in FULL recovery mode and only issue
Full backups. You need to issue regular (at least several times a day) LOG
backups in order for the log to truncate the committed transactions and
reuse the space. If you don't want to do Log backups then change the
recovery mode to SIMPLE and it will keep it in check for you.
Andrew J. Kelly SQL MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:u3917jGwFHA.3720@.TK2MSFTNGP14.phx.gbl...
> My database file is 55 MB. The transaction log is 14 GB. Do you
> recommend that I leave the transaction log alone? Thanks.
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:uKa26MFwFHA.2516@.TK2MSFTNGP12.phx.gbl...
>
Showing posts with label shrinkdb. Show all posts
Showing posts with label shrinkdb. Show all posts
Thursday, March 29, 2012
dbcc shrinkdb
hi,
I need to shring a SQL 2000 db by 50GB. Is it better to start sql in single
user mode when doing such action?I believe you will find that the database will be put into single user mode
for the life of your shrink session automatically. But it might simplify
matters to do it manually.
Joseph R.P. Maloney, CSP,CCP,CDP
"stoney" wrote:
> hi,
> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in sing
le
> user mode when doing such action?|||Thanks very much for your prompt response. Does the system have a better
performance if I shrink the database more often? Say if I shrink the
database every 3 months.
Thanks.
"jrpm" <jrpm@.discussions.microsoft.com> wrote in message
news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...[vbcol=seagreen]
>I believe you will find that the database will be put into single user mode
> for the life of your shrink session automatically. But it might simplify
> matters to do it manually.
>
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "stoney" wrote:
>|||In my humble opinion database server perform better with their logs shrunk
and stored in medias.
The data are more important than the logs.
and logs are overhead to database services
thats why a sound backup and restore strategy must implemented
thanks,
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"Diane Walker" wrote:
> Thanks very much for your prompt response. Does the system have a better
> performance if I shrink the database more often? Say if I shrink the
> database every 3 months.
> Thanks.
> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>
>|||Shrinking does not require the db to be in single user mode and there is
nothing that does that automatically.
Andrew J. Kelly SQL MVP
"jrpm" <jrpm@.discussions.microsoft.com> wrote in message
news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...[vbcol=seagreen]
>I believe you will find that the database will be put into single user mode
> for the life of your shrink session automatically. But it might simplify
> matters to do it manually.
>
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "stoney" wrote:
>|||Actually you get better performance if you don't shrink it at all in most
cases. If you need to keep shrinking it that is a pretty good indication it
wants to be larger than you think it should be. So leave it alone. See
this:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Andrew J. Kelly SQL MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
> Thanks very much for your prompt response. Does the system have a better
> performance if I shrink the database more often? Say if I shrink the
> database every 3 months.
> Thanks.
> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>|||Just the opposite. Transaction logs are crucial to performance on SQL
Server. Since all data manipulation is sent to the transaction log first it
will slow everything else down if it can not write fast enough. By
shrinking the log files too much you will force them to grow just when it
needs to write entries to the log file. They then must wait on that
operation to complete before they can continue.
Andrew J. Kelly SQL MVP
"Jose G. de Jesus Jr MCP, MCDBA" <Email me> wrote in message
news:986EDB0C-E8C8-47F5-8646-175E0CE40A22@.microsoft.com...[vbcol=seagreen]
> In my humble opinion database server perform better with their logs shrunk
> and stored in medias.
> The data are more important than the logs.
> and logs are overhead to database services
> thats why a sound backup and restore strategy must implemented
> --
> thanks,
> --
> Jose de Jesus Jr. Mcp,Mcdba
> Data Architect
> Sykes Asia (Manila philippines)
> MCP #2324787
>
> "Diane Walker" wrote:
>|||Thanks very much for the information.
"Jose G. de Jesus Jr MCP, MCDBA" <Email me> wrote in message
news:986EDB0C-E8C8-47F5-8646-175E0CE40A22@.microsoft.com...[vbcol=seagreen]
> In my humble opinion database server perform better with their logs shrunk
> and stored in medias.
> The data are more important than the logs.
> and logs are overhead to database services
> thats why a sound backup and restore strategy must implemented
> --
> thanks,
> --
> Jose de Jesus Jr. Mcp,Mcdba
> Data Architect
> Sykes Asia (Manila philippines)
> MCP #2324787
>
> "Diane Walker" wrote:
>|||My database file is 55 MB. The transaction log is 14 GB. Do you recommend
that I leave the transaction log alone? Thanks.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uKa26MFwFHA.2516@.TK2MSFTNGP12.phx.gbl...
> Actually you get better performance if you don't shrink it at all in most
> cases. If you need to keep shrinking it that is a pretty good indication
> it wants to be larger than you think it should be. So leave it alone.
> See this:
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> --
> Andrew J. Kelly SQL MVP
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
>|||No that is excessive and warrants a shrinking<g>. But why did it get there
in the first place? Chances are you are in FULL recovery mode and only issue
Full backups. You need to issue regular (at least several times a day) LOG
backups in order for the log to truncate the committed transactions and
reuse the space. If you don't want to do Log backups then change the
recovery mode to SIMPLE and it will keep it in check for you.
Andrew J. Kelly SQL MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:u3917jGwFHA.3720@.TK2MSFTNGP14.phx.gbl...
> My database file is 55 MB. The transaction log is 14 GB. Do you
> recommend that I leave the transaction log alone? Thanks.
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:uKa26MFwFHA.2516@.TK2MSFTNGP12.phx.gbl...
>
I need to shring a SQL 2000 db by 50GB. Is it better to start sql in single
user mode when doing such action?I believe you will find that the database will be put into single user mode
for the life of your shrink session automatically. But it might simplify
matters to do it manually.
Joseph R.P. Maloney, CSP,CCP,CDP
"stoney" wrote:
> hi,
> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in sing
le
> user mode when doing such action?|||Thanks very much for your prompt response. Does the system have a better
performance if I shrink the database more often? Say if I shrink the
database every 3 months.
Thanks.
"jrpm" <jrpm@.discussions.microsoft.com> wrote in message
news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...[vbcol=seagreen]
>I believe you will find that the database will be put into single user mode
> for the life of your shrink session automatically. But it might simplify
> matters to do it manually.
>
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "stoney" wrote:
>|||In my humble opinion database server perform better with their logs shrunk
and stored in medias.
The data are more important than the logs.
and logs are overhead to database services
thats why a sound backup and restore strategy must implemented
thanks,
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"Diane Walker" wrote:
> Thanks very much for your prompt response. Does the system have a better
> performance if I shrink the database more often? Say if I shrink the
> database every 3 months.
> Thanks.
> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>
>|||Shrinking does not require the db to be in single user mode and there is
nothing that does that automatically.
Andrew J. Kelly SQL MVP
"jrpm" <jrpm@.discussions.microsoft.com> wrote in message
news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...[vbcol=seagreen]
>I believe you will find that the database will be put into single user mode
> for the life of your shrink session automatically. But it might simplify
> matters to do it manually.
>
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "stoney" wrote:
>|||Actually you get better performance if you don't shrink it at all in most
cases. If you need to keep shrinking it that is a pretty good indication it
wants to be larger than you think it should be. So leave it alone. See
this:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Andrew J. Kelly SQL MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
> Thanks very much for your prompt response. Does the system have a better
> performance if I shrink the database more often? Say if I shrink the
> database every 3 months.
> Thanks.
> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>|||Just the opposite. Transaction logs are crucial to performance on SQL
Server. Since all data manipulation is sent to the transaction log first it
will slow everything else down if it can not write fast enough. By
shrinking the log files too much you will force them to grow just when it
needs to write entries to the log file. They then must wait on that
operation to complete before they can continue.
Andrew J. Kelly SQL MVP
"Jose G. de Jesus Jr MCP, MCDBA" <Email me> wrote in message
news:986EDB0C-E8C8-47F5-8646-175E0CE40A22@.microsoft.com...[vbcol=seagreen]
> In my humble opinion database server perform better with their logs shrunk
> and stored in medias.
> The data are more important than the logs.
> and logs are overhead to database services
> thats why a sound backup and restore strategy must implemented
> --
> thanks,
> --
> Jose de Jesus Jr. Mcp,Mcdba
> Data Architect
> Sykes Asia (Manila philippines)
> MCP #2324787
>
> "Diane Walker" wrote:
>|||Thanks very much for the information.
"Jose G. de Jesus Jr MCP, MCDBA" <Email me> wrote in message
news:986EDB0C-E8C8-47F5-8646-175E0CE40A22@.microsoft.com...[vbcol=seagreen]
> In my humble opinion database server perform better with their logs shrunk
> and stored in medias.
> The data are more important than the logs.
> and logs are overhead to database services
> thats why a sound backup and restore strategy must implemented
> --
> thanks,
> --
> Jose de Jesus Jr. Mcp,Mcdba
> Data Architect
> Sykes Asia (Manila philippines)
> MCP #2324787
>
> "Diane Walker" wrote:
>|||My database file is 55 MB. The transaction log is 14 GB. Do you recommend
that I leave the transaction log alone? Thanks.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uKa26MFwFHA.2516@.TK2MSFTNGP12.phx.gbl...
> Actually you get better performance if you don't shrink it at all in most
> cases. If you need to keep shrinking it that is a pretty good indication
> it wants to be larger than you think it should be. So leave it alone.
> See this:
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> --
> Andrew J. Kelly SQL MVP
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
>|||No that is excessive and warrants a shrinking<g>. But why did it get there
in the first place? Chances are you are in FULL recovery mode and only issue
Full backups. You need to issue regular (at least several times a day) LOG
backups in order for the log to truncate the committed transactions and
reuse the space. If you don't want to do Log backups then change the
recovery mode to SIMPLE and it will keep it in check for you.
Andrew J. Kelly SQL MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:u3917jGwFHA.3720@.TK2MSFTNGP14.phx.gbl...
> My database file is 55 MB. The transaction log is 14 GB. Do you
> recommend that I leave the transaction log alone? Thanks.
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:uKa26MFwFHA.2516@.TK2MSFTNGP12.phx.gbl...
>
dbcc shrinkdb
hi,
I need to shring a SQL 2000 db by 50GB. Is it better to start sql in single
user mode when doing such action?I believe you will find that the database will be put into single user mode
for the life of your shrink session automatically. But it might simplify
matters to do it manually.
Joseph R.P. Maloney, CSP,CCP,CDP
"stoney" wrote:
> hi,
> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in single
> user mode when doing such action?|||Thanks very much for your prompt response. Does the system have a better
performance if I shrink the database more often? Say if I shrink the
database every 3 months.
Thanks.
"jrpm" <jrpm@.discussions.microsoft.com> wrote in message
news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>I believe you will find that the database will be put into single user mode
> for the life of your shrink session automatically. But it might simplify
> matters to do it manually.
>
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "stoney" wrote:
>> hi,
>> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> single
>> user mode when doing such action?|||In my humble opinion database server perform better with their logs shrunk
and stored in medias.
The data are more important than the logs.
and logs are overhead to database services
thats why a sound backup and restore strategy must implemented
--
thanks,
--
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"Diane Walker" wrote:
> Thanks very much for your prompt response. Does the system have a better
> performance if I shrink the database more often? Say if I shrink the
> database every 3 months.
> Thanks.
> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
> >I believe you will find that the database will be put into single user mode
> > for the life of your shrink session automatically. But it might simplify
> > matters to do it manually.
> >
> >
> > --
> > Joseph R.P. Maloney, CSP,CCP,CDP
> >
> >
> > "stoney" wrote:
> >
> >> hi,
> >>
> >> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
> >> single
> >> user mode when doing such action?
>
>|||Shrinking does not require the db to be in single user mode and there is
nothing that does that automatically.
--
Andrew J. Kelly SQL MVP
"jrpm" <jrpm@.discussions.microsoft.com> wrote in message
news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>I believe you will find that the database will be put into single user mode
> for the life of your shrink session automatically. But it might simplify
> matters to do it manually.
>
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "stoney" wrote:
>> hi,
>> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> single
>> user mode when doing such action?|||Actually you get better performance if you don't shrink it at all in most
cases. If you need to keep shrinking it that is a pretty good indication it
wants to be larger than you think it should be. So leave it alone. See
this:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
--
Andrew J. Kelly SQL MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
> Thanks very much for your prompt response. Does the system have a better
> performance if I shrink the database more often? Say if I shrink the
> database every 3 months.
> Thanks.
> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>>I believe you will find that the database will be put into single user
>>mode
>> for the life of your shrink session automatically. But it might simplify
>> matters to do it manually.
>>
>> --
>> Joseph R.P. Maloney, CSP,CCP,CDP
>>
>> "stoney" wrote:
>> hi,
>> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> single
>> user mode when doing such action?
>|||Just the opposite. Transaction logs are crucial to performance on SQL
Server. Since all data manipulation is sent to the transaction log first it
will slow everything else down if it can not write fast enough. By
shrinking the log files too much you will force them to grow just when it
needs to write entries to the log file. They then must wait on that
operation to complete before they can continue.
--
Andrew J. Kelly SQL MVP
"Jose G. de Jesus Jr MCP, MCDBA" <Email me> wrote in message
news:986EDB0C-E8C8-47F5-8646-175E0CE40A22@.microsoft.com...
> In my humble opinion database server perform better with their logs shrunk
> and stored in medias.
> The data are more important than the logs.
> and logs are overhead to database services
> thats why a sound backup and restore strategy must implemented
> --
> thanks,
> --
> Jose de Jesus Jr. Mcp,Mcdba
> Data Architect
> Sykes Asia (Manila philippines)
> MCP #2324787
>
> "Diane Walker" wrote:
>> Thanks very much for your prompt response. Does the system have a better
>> performance if I shrink the database more often? Say if I shrink the
>> database every 3 months.
>> Thanks.
>> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
>> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>> >I believe you will find that the database will be put into single user
>> >mode
>> > for the life of your shrink session automatically. But it might
>> > simplify
>> > matters to do it manually.
>> >
>> >
>> > --
>> > Joseph R.P. Maloney, CSP,CCP,CDP
>> >
>> >
>> > "stoney" wrote:
>> >
>> >> hi,
>> >>
>> >> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> >> single
>> >> user mode when doing such action?
>>|||Thanks very much for the information.
"Jose G. de Jesus Jr MCP, MCDBA" <Email me> wrote in message
news:986EDB0C-E8C8-47F5-8646-175E0CE40A22@.microsoft.com...
> In my humble opinion database server perform better with their logs shrunk
> and stored in medias.
> The data are more important than the logs.
> and logs are overhead to database services
> thats why a sound backup and restore strategy must implemented
> --
> thanks,
> --
> Jose de Jesus Jr. Mcp,Mcdba
> Data Architect
> Sykes Asia (Manila philippines)
> MCP #2324787
>
> "Diane Walker" wrote:
>> Thanks very much for your prompt response. Does the system have a better
>> performance if I shrink the database more often? Say if I shrink the
>> database every 3 months.
>> Thanks.
>> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
>> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>> >I believe you will find that the database will be put into single user
>> >mode
>> > for the life of your shrink session automatically. But it might
>> > simplify
>> > matters to do it manually.
>> >
>> >
>> > --
>> > Joseph R.P. Maloney, CSP,CCP,CDP
>> >
>> >
>> > "stoney" wrote:
>> >
>> >> hi,
>> >>
>> >> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> >> single
>> >> user mode when doing such action?
>>|||My database file is 55 MB. The transaction log is 14 GB. Do you recommend
that I leave the transaction log alone? Thanks.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uKa26MFwFHA.2516@.TK2MSFTNGP12.phx.gbl...
> Actually you get better performance if you don't shrink it at all in most
> cases. If you need to keep shrinking it that is a pretty good indication
> it wants to be larger than you think it should be. So leave it alone.
> See this:
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> --
> Andrew J. Kelly SQL MVP
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
>> Thanks very much for your prompt response. Does the system have a better
>> performance if I shrink the database more often? Say if I shrink the
>> database every 3 months.
>> Thanks.
>> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
>> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>>I believe you will find that the database will be put into single user
>>mode
>> for the life of your shrink session automatically. But it might
>> simplify
>> matters to do it manually.
>>
>> --
>> Joseph R.P. Maloney, CSP,CCP,CDP
>>
>> "stoney" wrote:
>> hi,
>> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> single
>> user mode when doing such action?
>>
>|||No that is excessive and warrants a shrinking<g>. But why did it get there
in the first place? Chances are you are in FULL recovery mode and only issue
Full backups. You need to issue regular (at least several times a day) LOG
backups in order for the log to truncate the committed transactions and
reuse the space. If you don't want to do Log backups then change the
recovery mode to SIMPLE and it will keep it in check for you.
--
Andrew J. Kelly SQL MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:u3917jGwFHA.3720@.TK2MSFTNGP14.phx.gbl...
> My database file is 55 MB. The transaction log is 14 GB. Do you
> recommend that I leave the transaction log alone? Thanks.
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:uKa26MFwFHA.2516@.TK2MSFTNGP12.phx.gbl...
>> Actually you get better performance if you don't shrink it at all in most
>> cases. If you need to keep shrinking it that is a pretty good indication
>> it wants to be larger than you think it should be. So leave it alone.
>> See this:
>> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Diane Walker" <ett9300@.yahoo.com> wrote in message
>> news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
>> Thanks very much for your prompt response. Does the system have a
>> better performance if I shrink the database more often? Say if I shrink
>> the database every 3 months.
>> Thanks.
>> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
>> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>>I believe you will find that the database will be put into single user
>>mode
>> for the life of your shrink session automatically. But it might
>> simplify
>> matters to do it manually.
>>
>> --
>> Joseph R.P. Maloney, CSP,CCP,CDP
>>
>> "stoney" wrote:
>> hi,
>> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> single
>> user mode when doing such action?
>>
>>
>|||Thanks very much for your prompt response. I have no idea why the log file
gets that big. What should I be doing so that the log file would not get
this big? We have had this database for 1 year and 3 months. I am doing
the full backup everyday, running Backexec from Veritas.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OltiB%23HwFHA.3688@.tk2msftngp13.phx.gbl...
> No that is excessive and warrants a shrinking<g>. But why did it get
> there in the first place? Chances are you are in FULL recovery mode and
> only issue Full backups. You need to issue regular (at least several
> times a day) LOG backups in order for the log to truncate the committed
> transactions and reuse the space. If you don't want to do Log backups
> then change the recovery mode to SIMPLE and it will keep it in check for
> you.
> --
> Andrew J. Kelly SQL MVP
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:u3917jGwFHA.3720@.TK2MSFTNGP14.phx.gbl...
>> My database file is 55 MB. The transaction log is 14 GB. Do you
>> recommend that I leave the transaction log alone? Thanks.
>> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> news:uKa26MFwFHA.2516@.TK2MSFTNGP12.phx.gbl...
>> Actually you get better performance if you don't shrink it at all in
>> most cases. If you need to keep shrinking it that is a pretty good
>> indication it wants to be larger than you think it should be. So leave
>> it alone. See this:
>> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Diane Walker" <ett9300@.yahoo.com> wrote in message
>> news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
>> Thanks very much for your prompt response. Does the system have a
>> better performance if I shrink the database more often? Say if I
>> shrink the database every 3 months.
>> Thanks.
>> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
>> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>>I believe you will find that the database will be put into single user
>>mode
>> for the life of your shrink session automatically. But it might
>> simplify
>> matters to do it manually.
>>
>> --
>> Joseph R.P. Maloney, CSP,CCP,CDP
>>
>> "stoney" wrote:
>> hi,
>> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> single
>> user mode when doing such action?
>>
>>
>>
>|||I listed what I feel the issue was in the last post<g>. Change your
recovery mode to Simple if you don't do log backups.
--
Andrew J. Kelly SQL MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:u65jHzSwFHA.624@.TK2MSFTNGP11.phx.gbl...
> Thanks very much for your prompt response. I have no idea why the log
> file gets that big. What should I be doing so that the log file would not
> get this big? We have had this database for 1 year and 3 months. I am
> doing the full backup everyday, running Backexec from Veritas.
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:OltiB%23HwFHA.3688@.tk2msftngp13.phx.gbl...
>> No that is excessive and warrants a shrinking<g>. But why did it get
>> there in the first place? Chances are you are in FULL recovery mode and
>> only issue Full backups. You need to issue regular (at least several
>> times a day) LOG backups in order for the log to truncate the committed
>> transactions and reuse the space. If you don't want to do Log backups
>> then change the recovery mode to SIMPLE and it will keep it in check for
>> you.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Diane Walker" <ett9300@.yahoo.com> wrote in message
>> news:u3917jGwFHA.3720@.TK2MSFTNGP14.phx.gbl...
>> My database file is 55 MB. The transaction log is 14 GB. Do you
>> recommend that I leave the transaction log alone? Thanks.
>> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> news:uKa26MFwFHA.2516@.TK2MSFTNGP12.phx.gbl...
>> Actually you get better performance if you don't shrink it at all in
>> most cases. If you need to keep shrinking it that is a pretty good
>> indication it wants to be larger than you think it should be. So leave
>> it alone. See this:
>> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Diane Walker" <ett9300@.yahoo.com> wrote in message
>> news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
>> Thanks very much for your prompt response. Does the system have a
>> better performance if I shrink the database more often? Say if I
>> shrink the database every 3 months.
>> Thanks.
>> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
>> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>>I believe you will find that the database will be put into single user
>>mode
>> for the life of your shrink session automatically. But it might
>> simplify
>> matters to do it manually.
>>
>> --
>> Joseph R.P. Maloney, CSP,CCP,CDP
>>
>> "stoney" wrote:
>>> hi,
>>>
>>> I need to shring a SQL 2000 db by 50GB. Is it better to start sql
>>> in single
>>> user mode when doing such action?
>>
>>
>>
>>
>
I need to shring a SQL 2000 db by 50GB. Is it better to start sql in single
user mode when doing such action?I believe you will find that the database will be put into single user mode
for the life of your shrink session automatically. But it might simplify
matters to do it manually.
Joseph R.P. Maloney, CSP,CCP,CDP
"stoney" wrote:
> hi,
> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in single
> user mode when doing such action?|||Thanks very much for your prompt response. Does the system have a better
performance if I shrink the database more often? Say if I shrink the
database every 3 months.
Thanks.
"jrpm" <jrpm@.discussions.microsoft.com> wrote in message
news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>I believe you will find that the database will be put into single user mode
> for the life of your shrink session automatically. But it might simplify
> matters to do it manually.
>
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "stoney" wrote:
>> hi,
>> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> single
>> user mode when doing such action?|||In my humble opinion database server perform better with their logs shrunk
and stored in medias.
The data are more important than the logs.
and logs are overhead to database services
thats why a sound backup and restore strategy must implemented
--
thanks,
--
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"Diane Walker" wrote:
> Thanks very much for your prompt response. Does the system have a better
> performance if I shrink the database more often? Say if I shrink the
> database every 3 months.
> Thanks.
> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
> >I believe you will find that the database will be put into single user mode
> > for the life of your shrink session automatically. But it might simplify
> > matters to do it manually.
> >
> >
> > --
> > Joseph R.P. Maloney, CSP,CCP,CDP
> >
> >
> > "stoney" wrote:
> >
> >> hi,
> >>
> >> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
> >> single
> >> user mode when doing such action?
>
>|||Shrinking does not require the db to be in single user mode and there is
nothing that does that automatically.
--
Andrew J. Kelly SQL MVP
"jrpm" <jrpm@.discussions.microsoft.com> wrote in message
news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>I believe you will find that the database will be put into single user mode
> for the life of your shrink session automatically. But it might simplify
> matters to do it manually.
>
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "stoney" wrote:
>> hi,
>> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> single
>> user mode when doing such action?|||Actually you get better performance if you don't shrink it at all in most
cases. If you need to keep shrinking it that is a pretty good indication it
wants to be larger than you think it should be. So leave it alone. See
this:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
--
Andrew J. Kelly SQL MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
> Thanks very much for your prompt response. Does the system have a better
> performance if I shrink the database more often? Say if I shrink the
> database every 3 months.
> Thanks.
> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>>I believe you will find that the database will be put into single user
>>mode
>> for the life of your shrink session automatically. But it might simplify
>> matters to do it manually.
>>
>> --
>> Joseph R.P. Maloney, CSP,CCP,CDP
>>
>> "stoney" wrote:
>> hi,
>> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> single
>> user mode when doing such action?
>|||Just the opposite. Transaction logs are crucial to performance on SQL
Server. Since all data manipulation is sent to the transaction log first it
will slow everything else down if it can not write fast enough. By
shrinking the log files too much you will force them to grow just when it
needs to write entries to the log file. They then must wait on that
operation to complete before they can continue.
--
Andrew J. Kelly SQL MVP
"Jose G. de Jesus Jr MCP, MCDBA" <Email me> wrote in message
news:986EDB0C-E8C8-47F5-8646-175E0CE40A22@.microsoft.com...
> In my humble opinion database server perform better with their logs shrunk
> and stored in medias.
> The data are more important than the logs.
> and logs are overhead to database services
> thats why a sound backup and restore strategy must implemented
> --
> thanks,
> --
> Jose de Jesus Jr. Mcp,Mcdba
> Data Architect
> Sykes Asia (Manila philippines)
> MCP #2324787
>
> "Diane Walker" wrote:
>> Thanks very much for your prompt response. Does the system have a better
>> performance if I shrink the database more often? Say if I shrink the
>> database every 3 months.
>> Thanks.
>> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
>> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>> >I believe you will find that the database will be put into single user
>> >mode
>> > for the life of your shrink session automatically. But it might
>> > simplify
>> > matters to do it manually.
>> >
>> >
>> > --
>> > Joseph R.P. Maloney, CSP,CCP,CDP
>> >
>> >
>> > "stoney" wrote:
>> >
>> >> hi,
>> >>
>> >> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> >> single
>> >> user mode when doing such action?
>>|||Thanks very much for the information.
"Jose G. de Jesus Jr MCP, MCDBA" <Email me> wrote in message
news:986EDB0C-E8C8-47F5-8646-175E0CE40A22@.microsoft.com...
> In my humble opinion database server perform better with their logs shrunk
> and stored in medias.
> The data are more important than the logs.
> and logs are overhead to database services
> thats why a sound backup and restore strategy must implemented
> --
> thanks,
> --
> Jose de Jesus Jr. Mcp,Mcdba
> Data Architect
> Sykes Asia (Manila philippines)
> MCP #2324787
>
> "Diane Walker" wrote:
>> Thanks very much for your prompt response. Does the system have a better
>> performance if I shrink the database more often? Say if I shrink the
>> database every 3 months.
>> Thanks.
>> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
>> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>> >I believe you will find that the database will be put into single user
>> >mode
>> > for the life of your shrink session automatically. But it might
>> > simplify
>> > matters to do it manually.
>> >
>> >
>> > --
>> > Joseph R.P. Maloney, CSP,CCP,CDP
>> >
>> >
>> > "stoney" wrote:
>> >
>> >> hi,
>> >>
>> >> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> >> single
>> >> user mode when doing such action?
>>|||My database file is 55 MB. The transaction log is 14 GB. Do you recommend
that I leave the transaction log alone? Thanks.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uKa26MFwFHA.2516@.TK2MSFTNGP12.phx.gbl...
> Actually you get better performance if you don't shrink it at all in most
> cases. If you need to keep shrinking it that is a pretty good indication
> it wants to be larger than you think it should be. So leave it alone.
> See this:
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> --
> Andrew J. Kelly SQL MVP
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
>> Thanks very much for your prompt response. Does the system have a better
>> performance if I shrink the database more often? Say if I shrink the
>> database every 3 months.
>> Thanks.
>> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
>> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>>I believe you will find that the database will be put into single user
>>mode
>> for the life of your shrink session automatically. But it might
>> simplify
>> matters to do it manually.
>>
>> --
>> Joseph R.P. Maloney, CSP,CCP,CDP
>>
>> "stoney" wrote:
>> hi,
>> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> single
>> user mode when doing such action?
>>
>|||No that is excessive and warrants a shrinking<g>. But why did it get there
in the first place? Chances are you are in FULL recovery mode and only issue
Full backups. You need to issue regular (at least several times a day) LOG
backups in order for the log to truncate the committed transactions and
reuse the space. If you don't want to do Log backups then change the
recovery mode to SIMPLE and it will keep it in check for you.
--
Andrew J. Kelly SQL MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:u3917jGwFHA.3720@.TK2MSFTNGP14.phx.gbl...
> My database file is 55 MB. The transaction log is 14 GB. Do you
> recommend that I leave the transaction log alone? Thanks.
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:uKa26MFwFHA.2516@.TK2MSFTNGP12.phx.gbl...
>> Actually you get better performance if you don't shrink it at all in most
>> cases. If you need to keep shrinking it that is a pretty good indication
>> it wants to be larger than you think it should be. So leave it alone.
>> See this:
>> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Diane Walker" <ett9300@.yahoo.com> wrote in message
>> news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
>> Thanks very much for your prompt response. Does the system have a
>> better performance if I shrink the database more often? Say if I shrink
>> the database every 3 months.
>> Thanks.
>> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
>> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>>I believe you will find that the database will be put into single user
>>mode
>> for the life of your shrink session automatically. But it might
>> simplify
>> matters to do it manually.
>>
>> --
>> Joseph R.P. Maloney, CSP,CCP,CDP
>>
>> "stoney" wrote:
>> hi,
>> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> single
>> user mode when doing such action?
>>
>>
>|||Thanks very much for your prompt response. I have no idea why the log file
gets that big. What should I be doing so that the log file would not get
this big? We have had this database for 1 year and 3 months. I am doing
the full backup everyday, running Backexec from Veritas.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OltiB%23HwFHA.3688@.tk2msftngp13.phx.gbl...
> No that is excessive and warrants a shrinking<g>. But why did it get
> there in the first place? Chances are you are in FULL recovery mode and
> only issue Full backups. You need to issue regular (at least several
> times a day) LOG backups in order for the log to truncate the committed
> transactions and reuse the space. If you don't want to do Log backups
> then change the recovery mode to SIMPLE and it will keep it in check for
> you.
> --
> Andrew J. Kelly SQL MVP
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:u3917jGwFHA.3720@.TK2MSFTNGP14.phx.gbl...
>> My database file is 55 MB. The transaction log is 14 GB. Do you
>> recommend that I leave the transaction log alone? Thanks.
>> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> news:uKa26MFwFHA.2516@.TK2MSFTNGP12.phx.gbl...
>> Actually you get better performance if you don't shrink it at all in
>> most cases. If you need to keep shrinking it that is a pretty good
>> indication it wants to be larger than you think it should be. So leave
>> it alone. See this:
>> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Diane Walker" <ett9300@.yahoo.com> wrote in message
>> news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
>> Thanks very much for your prompt response. Does the system have a
>> better performance if I shrink the database more often? Say if I
>> shrink the database every 3 months.
>> Thanks.
>> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
>> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>>I believe you will find that the database will be put into single user
>>mode
>> for the life of your shrink session automatically. But it might
>> simplify
>> matters to do it manually.
>>
>> --
>> Joseph R.P. Maloney, CSP,CCP,CDP
>>
>> "stoney" wrote:
>> hi,
>> I need to shring a SQL 2000 db by 50GB. Is it better to start sql in
>> single
>> user mode when doing such action?
>>
>>
>>
>|||I listed what I feel the issue was in the last post<g>. Change your
recovery mode to Simple if you don't do log backups.
--
Andrew J. Kelly SQL MVP
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:u65jHzSwFHA.624@.TK2MSFTNGP11.phx.gbl...
> Thanks very much for your prompt response. I have no idea why the log
> file gets that big. What should I be doing so that the log file would not
> get this big? We have had this database for 1 year and 3 months. I am
> doing the full backup everyday, running Backexec from Veritas.
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:OltiB%23HwFHA.3688@.tk2msftngp13.phx.gbl...
>> No that is excessive and warrants a shrinking<g>. But why did it get
>> there in the first place? Chances are you are in FULL recovery mode and
>> only issue Full backups. You need to issue regular (at least several
>> times a day) LOG backups in order for the log to truncate the committed
>> transactions and reuse the space. If you don't want to do Log backups
>> then change the recovery mode to SIMPLE and it will keep it in check for
>> you.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Diane Walker" <ett9300@.yahoo.com> wrote in message
>> news:u3917jGwFHA.3720@.TK2MSFTNGP14.phx.gbl...
>> My database file is 55 MB. The transaction log is 14 GB. Do you
>> recommend that I leave the transaction log alone? Thanks.
>> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> news:uKa26MFwFHA.2516@.TK2MSFTNGP12.phx.gbl...
>> Actually you get better performance if you don't shrink it at all in
>> most cases. If you need to keep shrinking it that is a pretty good
>> indication it wants to be larger than you think it should be. So leave
>> it alone. See this:
>> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Diane Walker" <ett9300@.yahoo.com> wrote in message
>> news:OI6jb4EwFHA.4032@.TK2MSFTNGP15.phx.gbl...
>> Thanks very much for your prompt response. Does the system have a
>> better performance if I shrink the database more often? Say if I
>> shrink the database every 3 months.
>> Thanks.
>> "jrpm" <jrpm@.discussions.microsoft.com> wrote in message
>> news:E4CA50BF-C163-4968-82CD-E64AAAD20AD7@.microsoft.com...
>>I believe you will find that the database will be put into single user
>>mode
>> for the life of your shrink session automatically. But it might
>> simplify
>> matters to do it manually.
>>
>> --
>> Joseph R.P. Maloney, CSP,CCP,CDP
>>
>> "stoney" wrote:
>>> hi,
>>>
>>> I need to shring a SQL 2000 db by 50GB. Is it better to start sql
>>> in single
>>> user mode when doing such action?
>>
>>
>>
>>
>
Monday, March 19, 2012
DBCC memusage problem
When I use ShrinkDB or reindex and some other DB performance utilities, then when I use DBCC memusage it throws some error however it get corrected when I restart SQL Server
Is there any simplest way to correct this problem without restarting the SQL server
Regards
SunilCan you share the error? We might be able to debug this more easily.
--
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
"Sunil" <anonymous@.discussions.microsoft.com> wrote in message
news:41FCD39E-3F6F-44B7-88FE-31ADC023397B@.microsoft.com...
> When I use ShrinkDB or reindex and some other DB performance utilities,
then when I use DBCC memusage it throws some error however it get corrected
when I restart SQL Server.
>
> Is there any simplest way to correct this problem without restarting the
SQL server.
>
> Regards,
> Sunil|||This error is coming
--
Server: Msg 8966, Level 16, State 4, Line
Could not read and latch page (5:562) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1621) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1622) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1623) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1809) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1810) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1811) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1812) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1813) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1814) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1815) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1816) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1840) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1841) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1842) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1843) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1844) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1845) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1846) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1847) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1848) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1863) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1864) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1865) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1866) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1867) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1868) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1869) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1870) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1871) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1872) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1873) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1874) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1849) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1850) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1851) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1852) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1875) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1876) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1877) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1878) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1488) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1489) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1490) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1560) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1561) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1562) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1563) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1564) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1565) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1567) with latch type SH. VerifyPageId failed.
Could not read and latch page (1:811) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
BCC execution completed. If DBCC printed error messages, contact your system administrator.
Is there any simplest way to correct this problem without restarting the SQL server
Regards
SunilCan you share the error? We might be able to debug this more easily.
--
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
"Sunil" <anonymous@.discussions.microsoft.com> wrote in message
news:41FCD39E-3F6F-44B7-88FE-31ADC023397B@.microsoft.com...
> When I use ShrinkDB or reindex and some other DB performance utilities,
then when I use DBCC memusage it throws some error however it get corrected
when I restart SQL Server.
>
> Is there any simplest way to correct this problem without restarting the
SQL server.
>
> Regards,
> Sunil|||This error is coming
--
Server: Msg 8966, Level 16, State 4, Line
Could not read and latch page (5:562) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1621) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1622) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1623) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1809) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1810) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1811) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1812) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1813) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1814) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1815) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1816) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1840) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1841) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1842) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1843) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1844) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1845) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1846) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1847) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1848) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1863) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1864) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1865) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1866) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1867) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1868) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1869) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1870) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1871) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1872) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1873) with latch type SH. VerifyPageId failed
Server: Msg 8966, Level 16, State 1, Line
Could not read and latch page (8:1874) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1849) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1850) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1851) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1852) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1875) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1876) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1877) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1878) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1488) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1489) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1490) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1560) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1561) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1562) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1563) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1564) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1565) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1567) with latch type SH. VerifyPageId failed.
Could not read and latch page (1:811) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
BCC execution completed. If DBCC printed error messages, contact your system administrator.
DBCC memusage problem
When I use ShrinkDB or reindex and some other DB performance utilities, then
when I use DBCC memusage it throws some error however it get corrected when
I restart SQL Server.
Is there any simplest way to correct this problem without restarting the SQL
server.
Regards,
SunilCan you share the error? We might be able to debug this more easily.
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
"Sunil" <anonymous@.discussions.microsoft.com> wrote in message
news:41FCD39E-3F6F-44B7-88FE-31ADC023397B@.microsoft.com...
> When I use ShrinkDB or reindex and some other DB performance utilities,
then when I use DBCC memusage it throws some error however it get corrected
when I restart SQL Server.
>
> Is there any simplest way to correct this problem without restarting the
SQL server.
>
> Regards,
> Sunil|||This error is coming :
--
Server: Msg 8966, Level 16, State 4, Line 1
Could not read and latch page (5:562) with latch type SH. VerifyPageId faile
d.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1621) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1622) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1623) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1809) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1810) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1811) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1812) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1813) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1814) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1815) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1816) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1840) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1841) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1842) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1843) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1844) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1845) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1846) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1847) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1848) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1863) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1864) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1865) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1866) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1867) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1868) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1869) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1870) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1871) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1872) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1873) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1874) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1849) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1850) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1851) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1852) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1875) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1876) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1877) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1878) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1488) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1489) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1490) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1560) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1561) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1562) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1563) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1564) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1565) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1567) with latch type SH. VerifyPageId fail
ed.
Could not read and latch page (1:811) with latch type SH. VerifyPageId faile
d.
Server: Msg 8966, Level 16, State 1, Line 1
BCC execution completed. If DBCC printed error messages, contact your system
administrator.
when I use DBCC memusage it throws some error however it get corrected when
I restart SQL Server.
Is there any simplest way to correct this problem without restarting the SQL
server.
Regards,
SunilCan you share the error? We might be able to debug this more easily.
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
"Sunil" <anonymous@.discussions.microsoft.com> wrote in message
news:41FCD39E-3F6F-44B7-88FE-31ADC023397B@.microsoft.com...
> When I use ShrinkDB or reindex and some other DB performance utilities,
then when I use DBCC memusage it throws some error however it get corrected
when I restart SQL Server.
>
> Is there any simplest way to correct this problem without restarting the
SQL server.
>
> Regards,
> Sunil|||This error is coming :
--
Server: Msg 8966, Level 16, State 4, Line 1
Could not read and latch page (5:562) with latch type SH. VerifyPageId faile
d.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1621) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1622) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1623) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1809) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1810) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1811) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1812) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1813) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1814) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1815) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1816) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1840) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1841) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1842) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1843) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1844) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1845) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1846) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1847) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1848) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1863) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1864) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1865) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1866) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1867) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1868) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1869) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1870) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1871) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1872) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1873) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1874) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1849) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1850) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1851) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1852) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1875) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1876) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1877) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1878) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1488) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1489) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1490) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1560) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1561) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1562) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1563) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1564) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1565) with latch type SH. VerifyPageId fail
ed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1567) with latch type SH. VerifyPageId fail
ed.
Could not read and latch page (1:811) with latch type SH. VerifyPageId faile
d.
Server: Msg 8966, Level 16, State 1, Line 1
BCC execution completed. If DBCC printed error messages, contact your system
administrator.
DBCC memusage problem
When I use ShrinkDB or reindex and some other DB performance utilities, then when I use DBCC memusage it throws some error however it get corrected when I restart SQL Server.
Is there any simplest way to correct this problem without restarting the SQL server.
Regards,
Sunil
Can you share the error? We might be able to debug this more easily.
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
"Sunil" <anonymous@.discussions.microsoft.com> wrote in message
news:41FCD39E-3F6F-44B7-88FE-31ADC023397B@.microsoft.com...
> When I use ShrinkDB or reindex and some other DB performance utilities,
then when I use DBCC memusage it throws some error however it get corrected
when I restart SQL Server.
>
> Is there any simplest way to correct this problem without restarting the
SQL server.
>
> Regards,
> Sunil
|||This error is coming :
Server: Msg 8966, Level 16, State 4, Line 1
Could not read and latch page (5:562) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1621) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1622) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1623) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1809) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1810) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1811) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1812) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1813) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1814) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1815) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1816) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1840) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1841) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1842) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1843) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1844) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1845) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1846) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1847) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1848) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1863) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1864) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1865) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1866) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1867) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1868) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1869) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1870) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1871) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1872) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1873) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1874) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1849) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1850) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1851) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1852) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1875) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1876) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1877) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1878) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1488) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1489) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1490) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1560) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1561) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1562) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1563) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1564) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1565) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1567) with latch type SH. VerifyPageId failed.
Could not read and latch page (1:811) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
BCC execution completed. If DBCC printed error messages, contact your system administrator.
Is there any simplest way to correct this problem without restarting the SQL server.
Regards,
Sunil
Can you share the error? We might be able to debug this more easily.
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
"Sunil" <anonymous@.discussions.microsoft.com> wrote in message
news:41FCD39E-3F6F-44B7-88FE-31ADC023397B@.microsoft.com...
> When I use ShrinkDB or reindex and some other DB performance utilities,
then when I use DBCC memusage it throws some error however it get corrected
when I restart SQL Server.
>
> Is there any simplest way to correct this problem without restarting the
SQL server.
>
> Regards,
> Sunil
|||This error is coming :
Server: Msg 8966, Level 16, State 4, Line 1
Could not read and latch page (5:562) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1621) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1622) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1623) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1809) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1810) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1811) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1812) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1813) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1814) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1815) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1816) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1840) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1841) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1842) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1843) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1844) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1845) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1846) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1847) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1848) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1863) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1864) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1865) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1866) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1867) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1868) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1869) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1870) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1871) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1872) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1873) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1874) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1849) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1850) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1851) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1852) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1875) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1876) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1877) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1878) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1488) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1489) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1490) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1560) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1561) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1562) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1563) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1564) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1565) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (8:1567) with latch type SH. VerifyPageId failed.
Could not read and latch page (1:811) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
BCC execution completed. If DBCC printed error messages, contact your system administrator.
Subscribe to:
Posts (Atom)