On Jul 22, 1:35 pm, liezl...@gmail.com wrote:
> > On Jul 21, 10:28 am, liezl...@gmail.com wrote:
>
[quoted text clipped - 83 lines]
>
> - Show quoted text -
The server wide locking scheme was changed by mistake after
installation, so the table was created with the DATA ONLY LOCKED
scheme, however, it still reported ALLPAGES in the sp_help output.
I didn't check the the server wide setting and assumed this was either
datarows or datapages.
Since then, one of the DBA's changed it on the fly back to ALLPAGES,
and the above command worked again with the sorted_data option.
...Yes, Luckily this was not production!
Thanks again
Liz
Carl Kayser - 25 Jul 2008 17:30 GMT
On Jul 22, 1:35 pm, liezl...@gmail.com wrote:
> On Jul 21, 8:25 pm, Bret_Halford <b...@sybase.com> wrote:
>
[quoted text clipped - 85 lines]
>
> - Show quoted text -
The server wide locking scheme was changed by mistake after
installation, so the table was created with the DATA ONLY LOCKED
scheme, however, it still reported ALLPAGES in the sp_help output.
I didn't check the the server wide setting and assumed this was either
datarows or datapages.
Since then, one of the DBA's changed it on the fly back to ALLPAGES,
and the above command worked again with the sorted_data option.
...Yes, Luckily this was not production!
Thanks again
Liz
Perhaps I am missing something here. I assume that the table was created
after the deafult server locking scheme was set to DOL. In which case there
is a bug with sp_help. Right? Changing the default locking scheme
shouldn't affect drop/create index; the lock scheme is an attribute of the
table. I find the above described scenario to be inconsistent.