I'm looking for explanations and troubleshooting
documentation for analyzing SQL Server waits (output from
dbcc sqlperf(waitstats)) other than from this paper:
http://support.microsoft.com/default.aspx?scid=KB;en-
us;q244455
Does anyone have anything more current? Thanks.
RobWhat is it specifically you are looking for? Specific
wait types?
If you are concerned with specific waitstats, and do not
know what the waistat is, then search on www.deja.com. It
is a good resource.
Greg
>--Original Message--
>I'm looking for explanations and troubleshooting
>documentation for analyzing SQL Server waits (output from
>dbcc sqlperf(waitstats)) other than from this paper:
>http://support.microsoft.com/default.aspx?scid=KB;en-
>us;q244455
>Does anyone have anything more current? Thanks.
>Rob
>.
>
Showing posts with label documentation. Show all posts
Showing posts with label documentation. Show all posts
Monday, March 26, 2012
Monday, March 19, 2012
indexing document stored in IMAGE fields
Hi guys,
in the Full Text Retrieval documentation of MS SQLserver 2000 it's said that the document stored in IMAGE
fields are "filtered" using the Microsoft provided filters (for these file extensions: .doc, .xls, .ppt, .txt
and .htm) or third party filters (e.g. Adobe for .pdf).
Little after there's a note stating that "For full-text indexing, a document must be less than 16 megabytes (MB)
in size and must not contain more than 256 kilobytes (KB) of filtered text.".
While I can check if a file is larger than the max supported size, how can I check if a document contains more
than 256 KB of filtered text ? Is this information "exported" in some way by the filter applied to the document ?
If I store a document that does not satisfy the MSSearch requirements (size > 16MB or "filtered size" > 256 KB), which
actions are made by MSSearch ? Does indexing simply ignore it ?
Many THXS for your kind reply
MadMax
The best way to do this is to get filtdump from the platform sdk and do this
filtdump -b mydoc.doc >c:\out.out and then measure the size of the output.
In other versions of Microsoft Search products there were limits of the amount fo text per document that would be indexed. You could adjust this with a registry key setting. Any bytes over this interval would not be retrieved or indexed.
There are settings within MSSearch which allows you to control the maximum raw size of a document you are indexing but AFAIK there is no setting to allow you to increase the maximum amount of textual data it will index.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||THX very much Hilary.
Do you know what happen if the indexed document is bigger than the MSSearch limits (size 16MB, filtered size 256KB) ?
Is the document indexed (may be only for the part <16MB / filtered size < 256) or the indexing process fails completely ?
Max
|||My understanding is that only the first 16 M is extracted and only the first 256 k of text indexed.
The rest is ingnored.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||Max, Hilary,
I posted this reply in Nov. 2003, on this same subject... "I believe that
this is a DOC bug, i.e., a bug or incorrect information in
Books Online (BOL). To the best of my knowledge, no public KB exists for
this bug, however a related KB article - 308771 (Q308771) "PRB: A Full-Text
Search May Not Return Any Hits If It Fails to Index a File" at
http://support.microsoft.com/default...b;en-us;308771 has
information on the use of the Registry key: FilterProcessMemoryQuota.
You can control the size of the FT Index doc via Registry Key
FilterProcessMemoryQuota and setting it's value. Specifically,
HKLM\Software\Microsoft\Search\1.0\gathering
manager\filterProcessMemoryQuota, (DWORD).
It should default to 25MB and you can make it larger as it only affects the
limit for memory usage in the daemon [MSSdmn] process. In addition to the
memory allocated to SQL Server, it is recommended that a minimum of 15 MB of
RAM be reserved for the Microsoft Search service and a maximum of 512 MB of
RAM be allocated for the Microsoft Search service. If you plan on FT
Indexing large documents, you will need to set aside more memory for the
"Microsoft Search" (mssearch.exe) service and TEST the performance FT
Indexing very large documents as well as ensure that you have enough free
disk space on you system drive and the drive where your FT Catalogs reside
at all times."
Regards,
John
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:32335399-ADC7-45AD-B179-8D97C46CBC73@.microsoft.com...
> My understanding is that only the first 16 M is extracted and only the
first 256 k of text indexed.
> The rest is ingnored.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
in the Full Text Retrieval documentation of MS SQLserver 2000 it's said that the document stored in IMAGE
fields are "filtered" using the Microsoft provided filters (for these file extensions: .doc, .xls, .ppt, .txt
and .htm) or third party filters (e.g. Adobe for .pdf).
Little after there's a note stating that "For full-text indexing, a document must be less than 16 megabytes (MB)
in size and must not contain more than 256 kilobytes (KB) of filtered text.".
While I can check if a file is larger than the max supported size, how can I check if a document contains more
than 256 KB of filtered text ? Is this information "exported" in some way by the filter applied to the document ?
If I store a document that does not satisfy the MSSearch requirements (size > 16MB or "filtered size" > 256 KB), which
actions are made by MSSearch ? Does indexing simply ignore it ?
Many THXS for your kind reply
MadMax
The best way to do this is to get filtdump from the platform sdk and do this
filtdump -b mydoc.doc >c:\out.out and then measure the size of the output.
In other versions of Microsoft Search products there were limits of the amount fo text per document that would be indexed. You could adjust this with a registry key setting. Any bytes over this interval would not be retrieved or indexed.
There are settings within MSSearch which allows you to control the maximum raw size of a document you are indexing but AFAIK there is no setting to allow you to increase the maximum amount of textual data it will index.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||THX very much Hilary.
Do you know what happen if the indexed document is bigger than the MSSearch limits (size 16MB, filtered size 256KB) ?
Is the document indexed (may be only for the part <16MB / filtered size < 256) or the indexing process fails completely ?
Max
|||My understanding is that only the first 16 M is extracted and only the first 256 k of text indexed.
The rest is ingnored.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||Max, Hilary,
I posted this reply in Nov. 2003, on this same subject... "I believe that
this is a DOC bug, i.e., a bug or incorrect information in
Books Online (BOL). To the best of my knowledge, no public KB exists for
this bug, however a related KB article - 308771 (Q308771) "PRB: A Full-Text
Search May Not Return Any Hits If It Fails to Index a File" at
http://support.microsoft.com/default...b;en-us;308771 has
information on the use of the Registry key: FilterProcessMemoryQuota.
You can control the size of the FT Index doc via Registry Key
FilterProcessMemoryQuota and setting it's value. Specifically,
HKLM\Software\Microsoft\Search\1.0\gathering
manager\filterProcessMemoryQuota, (DWORD).
It should default to 25MB and you can make it larger as it only affects the
limit for memory usage in the daemon [MSSdmn] process. In addition to the
memory allocated to SQL Server, it is recommended that a minimum of 15 MB of
RAM be reserved for the Microsoft Search service and a maximum of 512 MB of
RAM be allocated for the Microsoft Search service. If you plan on FT
Indexing large documents, you will need to set aside more memory for the
"Microsoft Search" (mssearch.exe) service and TEST the performance FT
Indexing very large documents as well as ensure that you have enough free
disk space on you system drive and the drive where your FT Catalogs reside
at all times."
Regards,
John
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:32335399-ADC7-45AD-B179-8D97C46CBC73@.microsoft.com...
> My understanding is that only the first 16 M is extracted and only the
first 256 k of text indexed.
> The rest is ingnored.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
Sunday, February 19, 2012
Indexed Views are they supported?
According the documentation in 2000 and 2005 indexed views are only supporte
d
in the Enterprise edition. So please explain why I can create a unique
clustered index on a view that is schemabound on the standard edition of SQL
Server 2000? Is an index on a view different then and indexed view? If so
please explain. Could it be that creating indexed views is supported in all
versions, but only the using the GUI (EM or Management Studio) to create the
views is not supported in Enterprise and Developer edition? I noticed that
"Manage Indexes...", is grayed out of the "All Tasks" drop down on a view in
EM, and I am running standard edition.You can create the index on any edition, however on the lower editions, it
will not be automatically considered in the query plan unless you use a
specific hint in the query.
"Greg Larsen" <GregLarsen@.discussions.microsoft.com> wrote in message
news:9A56678F-407D-41B2-BD4B-5A95C259EA97@.microsoft.com...
> According the documentation in 2000 and 2005 indexed views are only
> supported
> in the Enterprise edition. So please explain why I can create a unique
> clustered index on a view that is schemabound on the standard edition of
> SQL
> Server 2000? Is an index on a view different then and indexed view? If
> so
> please explain. Could it be that creating indexed views is supported in
> all
> versions, but only the using the GUI (EM or Management Studio) to create
> the
> views is not supported in Enterprise and Developer edition? I noticed
> that
> "Manage Indexes...", is grayed out of the "All Tasks" drop down on a view
> in
> EM, and I am running standard edition.|||So why is "Managed Indexes" grayed out in EM?
"Aaron Bertrand [SQL Server MVP]" wrote:
> You can create the index on any edition, however on the lower editions, it
> will not be automatically considered in the query plan unless you use a
> specific hint in the query.
>
>
> "Greg Larsen" <GregLarsen@.discussions.microsoft.com> wrote in message
> news:9A56678F-407D-41B2-BD4B-5A95C259EA97@.microsoft.com...
>
>|||> So why is "Managed Indexes" grayed out in EM?
I have no idea; I use EM for managing jobs and DTS and that's about it.
Stretching here, because I honestly don't believe EM is this smart, but is
it possible that this indexed view has the only index in the database?
A|||On Wed, 19 Apr 2006 09:17:03 -0700, Greg Larsen wrote:
>So why is "Managed Indexes" grayed out in EM?
Hi Greg,
I just ran a quick test on my copy of EM (connected to a developer
edition of SQL Server 2000). If I create a view with schemabinding, I
can access the "Manage indexes" option in EM. If I drop the view and
recreate it without schemabinding, then (after refreshing the list of
views) the "Manage indexes" option is greyed out.
Have yoou tried it on a view that was created with schemabinding and
that further also satisfies all requirements for creating an indexed
view?
Hugo Kornelis, SQL Server MVP
d
in the Enterprise edition. So please explain why I can create a unique
clustered index on a view that is schemabound on the standard edition of SQL
Server 2000? Is an index on a view different then and indexed view? If so
please explain. Could it be that creating indexed views is supported in all
versions, but only the using the GUI (EM or Management Studio) to create the
views is not supported in Enterprise and Developer edition? I noticed that
"Manage Indexes...", is grayed out of the "All Tasks" drop down on a view in
EM, and I am running standard edition.You can create the index on any edition, however on the lower editions, it
will not be automatically considered in the query plan unless you use a
specific hint in the query.
"Greg Larsen" <GregLarsen@.discussions.microsoft.com> wrote in message
news:9A56678F-407D-41B2-BD4B-5A95C259EA97@.microsoft.com...
> According the documentation in 2000 and 2005 indexed views are only
> supported
> in the Enterprise edition. So please explain why I can create a unique
> clustered index on a view that is schemabound on the standard edition of
> SQL
> Server 2000? Is an index on a view different then and indexed view? If
> so
> please explain. Could it be that creating indexed views is supported in
> all
> versions, but only the using the GUI (EM or Management Studio) to create
> the
> views is not supported in Enterprise and Developer edition? I noticed
> that
> "Manage Indexes...", is grayed out of the "All Tasks" drop down on a view
> in
> EM, and I am running standard edition.|||So why is "Managed Indexes" grayed out in EM?
"Aaron Bertrand [SQL Server MVP]" wrote:
> You can create the index on any edition, however on the lower editions, it
> will not be automatically considered in the query plan unless you use a
> specific hint in the query.
>
>
> "Greg Larsen" <GregLarsen@.discussions.microsoft.com> wrote in message
> news:9A56678F-407D-41B2-BD4B-5A95C259EA97@.microsoft.com...
>
>|||> So why is "Managed Indexes" grayed out in EM?
I have no idea; I use EM for managing jobs and DTS and that's about it.
Stretching here, because I honestly don't believe EM is this smart, but is
it possible that this indexed view has the only index in the database?
A|||On Wed, 19 Apr 2006 09:17:03 -0700, Greg Larsen wrote:
>So why is "Managed Indexes" grayed out in EM?
Hi Greg,
I just ran a quick test on my copy of EM (connected to a developer
edition of SQL Server 2000). If I create a view with schemabinding, I
can access the "Manage indexes" option in EM. If I drop the view and
recreate it without schemabinding, then (after refreshing the list of
views) the "Manage indexes" option is greyed out.
Have yoou tried it on a view that was created with schemabinding and
that further also satisfies all requirements for creating an indexed
view?
Hugo Kornelis, SQL Server MVP
Subscribe to:
Posts (Atom)