Showing posts with label index. Show all posts
Showing posts with label index. Show all posts

Wednesday, March 21, 2012

Parallel Index Operations

Got the following error messages when rebuilding indexes on SQL Server 2000 + SP3 server.
WARNING: EC 5c166098, 2 waited 300 sec. on latch 5c1694bc. Not a BUF latch.
Waiting for type 0x2, current count 0xa, current owning EC 0x5C16A098.
Refer to KB-810195, but it should be corrected in SP3. My server has already service pack 3 installed.
Johnny
We have seen this in relation to IO problems, have you checked the windows
system event log?
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:087B2B6A-32A4-4C14-841D-4FE2993B8E75@.microsoft.com...
> Got the following error messages when rebuilding indexes on SQL Server
2000 + SP3 server.
> WARNING: EC 5c166098, 2 waited 300 sec. on latch 5c1694bc. Not a BUF
latch.
> Waiting for type 0x2, current count 0xa, current owning EC 0x5C16A098.
> Refer to KB-810195, but it should be corrected in SP3. My server has
already service pack 3 installed.
> Johnny
>
|||There is no errors in the system & application event log around the time of running index rebuild.

Parallel Index Operations

Got the following error messages when rebuilding indexes on SQL Server 2000
+ SP3 server.
WARNING: EC 5c166098, 2 waited 300 sec. on latch 5c1694bc. Not a BUF latch.
Waiting for type 0x2, current count 0xa, current owning EC 0x5C16A098.
Refer to KB-810195, but it should be corrected in SP3. My server has alread
y service pack 3 installed.
JohnnyWe have seen this in relation to IO problems, have you checked the windows
system event log?
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:087B2B6A-32A4-4C14-841D-4FE2993B8E75@.microsoft.com...
> Got the following error messages when rebuilding indexes on SQL Server
2000 + SP3 server.
> WARNING: EC 5c166098, 2 waited 300 sec. on latch 5c1694bc. Not a BUF
latch.
> Waiting for type 0x2, current count 0xa, current owning EC 0x5C16A098.
> Refer to KB-810195, but it should be corrected in SP3. My server has
already service pack 3 installed.
> Johnny
>|||There is no errors in the system & application event log around the time of
running index rebuild.

Parallel Index Operations

Got the following error messages when rebuilding indexes on SQL Server 2000 + SP3 server.
WARNING: EC 5c166098, 2 waited 300 sec. on latch 5c1694bc. Not a BUF latch.
Waiting for type 0x2, current count 0xa, current owning EC 0x5C16A098.
Refer to KB-810195, but it should be corrected in SP3. My server has already service pack 3 installed.
JohnnyWe have seen this in relation to IO problems, have you checked the windows
system event log?
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:087B2B6A-32A4-4C14-841D-4FE2993B8E75@.microsoft.com...
> Got the following error messages when rebuilding indexes on SQL Server
2000 + SP3 server.
> WARNING: EC 5c166098, 2 waited 300 sec. on latch 5c1694bc. Not a BUF
latch.
> Waiting for type 0x2, current count 0xa, current owning EC 0x5C16A098.
> Refer to KB-810195, but it should be corrected in SP3. My server has
already service pack 3 installed.
> Johnny
>|||There is no errors in the system & application event log around the time of running index rebuild.

Tuesday, March 20, 2012

Parallel CREATE INDEX

This is apparently supported by Enterprise edition, but not by Standard
edition.
I've had a look at BOL, but am none the wiser. What does this mean exactly?
Does it mean that I can't get the standard edition to run two or more create
index commands at the same time? If so, what would happen if I attempted to
do that? Would all but the first get ignored or would SQLServer simply
queue them to run them sequentially?
Thanks
Griff
They're referring to using multiple CPU's to build the same index.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Griff" <Howling@.The.Moon> wrote in message
news:Oc49pdjfEHA.4092@.TK2MSFTNGP10.phx.gbl...
This is apparently supported by Enterprise edition, but not by Standard
edition.
I've had a look at BOL, but am none the wiser. What does this mean exactly?
Does it mean that I can't get the standard edition to run two or more create
index commands at the same time? If so, what would happen if I attempted to
do that? Would all but the first get ignored or would SQLServer simply
queue them to run them sequentially?
Thanks
Griff

Parallel CREATE INDEX

This is apparently supported by Enterprise edition, but not by Standard
edition.
I've had a look at BOL, but am none the wiser. What does this mean exactly?
Does it mean that I can't get the standard edition to run two or more create
index commands at the same time? If so, what would happen if I attempted to
do that? Would all but the first get ignored or would SQLServer simply
queue them to run them sequentially?
Thanks
GriffThey're referring to using multiple CPU's to build the same index.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Griff" <Howling@.The.Moon> wrote in message
news:Oc49pdjfEHA.4092@.TK2MSFTNGP10.phx.gbl...
This is apparently supported by Enterprise edition, but not by Standard
edition.
I've had a look at BOL, but am none the wiser. What does this mean exactly?
Does it mean that I can't get the standard edition to run two or more create
index commands at the same time? If so, what would happen if I attempted to
do that? Would all but the first get ignored or would SQLServer simply
queue them to run them sequentially?
Thanks
Griff

Parallel CREATE INDEX

This is apparently supported by Enterprise edition, but not by Standard
edition.
I've had a look at BOL, but am none the wiser. What does this mean exactly?
Does it mean that I can't get the standard edition to run two or more create
index commands at the same time? If so, what would happen if I attempted to
do that? Would all but the first get ignored or would SQLServer simply
queue them to run them sequentially?
Thanks
GriffThey're referring to using multiple CPU's to build the same index.
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Griff" <Howling@.The.Moon> wrote in message
news:Oc49pdjfEHA.4092@.TK2MSFTNGP10.phx.gbl...
This is apparently supported by Enterprise edition, but not by Standard
edition.
I've had a look at BOL, but am none the wiser. What does this mean exactly?
Does it mean that I can't get the standard edition to run two or more create
index commands at the same time? If so, what would happen if I attempted to
do that? Would all but the first get ignored or would SQLServer simply
queue them to run them sequentially?
Thanks
Griff

Saturday, February 25, 2012

Page Subtotals (Not Cumulative)

Hello,

I want to display subtotals for a column only for that page. Like;

Index Value

--

1 4

2 5

Subtotal 9

-

3 1

4 2

Subtotal 3

Total 12

RunningValue gives cumulative totals. I need subtotals for each visible page only. Is there a way to do it ?

Constraints:

I'm using a table. And I shouldn't use page breaks on my report.

Thanks in advance

Insert/ Add the Page Footer to the report. Now, inser another text box and the expression for this will be

=Sum(ReportItems!textbox6.Value)

TextBox6 is the field which contains the value, More information about this can be found at

http://technet.microsoft.com/en-us/library/ms159677.aspx

|||Thank you for your reply, Techquest.

It is solution for what I asked. But I need something different. I shouldn't use page footer or header either. I'm limited with the page body.