| Author |
Catalog Import - CS2K
|
|
| Mark Pope 2004-04-22, 3:37 pm |
| Everytime we import content into the catalog from an XML file we experience
timeout issues on the website.
Points to note:
1. The import is started using the CS CatalogManager.ImportXML method.
2. The actual import works fine but at the same time as CS executes an
update to the SQL free-text catalog we experience locking & timeouts.
3. The physical xml file varies in size, from about 8KB - 1MB but always the
same issue occurs.
4. The catalog only has a single property tagged for inclusion within the
full-text search which is a VARCHAR(255) datatype.
5. SQL Server sp_locks highlights the locking originating from an
application named "PKM" as below:
78 0 NT AUTHORITY\SYSTEM Catalog runnable 0 SELECT
PKM
1468 NETWORKIO
62 0 3 2004-03-23 19:31:01.977 1900-01-01 00:00:00.000 DBSERVER
TCP/IP 0006A348D942 0 1
6. HP Premier Support have suggested recreating the full-text catalog on the
table. Which has been done.
7. They also requested the full-text service being run under a domain level
user account instead of localsystem. That has also been done.
Any additional information can be provided, and any help would be very much
appreciated.
Thanks
Mark
| |
| Vinayak Tadas [MS] 2004-04-22, 4:38 pm |
| At the end of the import process the CatalogManager.ImportXml method
refreshes the full text indexes. As you figured out this is causing the
locks.
I am not sure if this will help you but in CS2002 we added a parameter on
the ImportXml which will turn off generating the fulltext indexes thereby
skipping the last step of the import.
Thanks
Vinayak Tadas
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2002 Microsoft Corporation. All rights
reserved.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Get Secure! For more info visit http://www.microsoft.com/security. Please
reply to the newsgroups only. Thanks
"Mark Pope" <MPope@datamonitor.com> wrote in message
news:e0WyEHKKEHA.204@TK2MSFTNGP10.phx.gbl...
> Everytime we import content into the catalog from an XML file we
experience
> timeout issues on the website.
>
> Points to note:
> 1. The import is started using the CS CatalogManager.ImportXML method.
> 2. The actual import works fine but at the same time as CS executes an
> update to the SQL free-text catalog we experience locking & timeouts.
> 3. The physical xml file varies in size, from about 8KB - 1MB but always
the
> same issue occurs.
> 4. The catalog only has a single property tagged for inclusion within the
> full-text search which is a VARCHAR(255) datatype.
> 5. SQL Server sp_locks highlights the locking originating from an
> application named "PKM" as below:
>
> 78 0 NT AUTHORITY\SYSTEM Catalog runnable 0 SELECT
> PKM
> 1468 NETWORKIO
> 62 0 3 2004-03-23 19:31:01.977 1900-01-01 00:00:00.000 DBSERVER
> TCP/IP 0006A348D942 0 1
>
> 6. HP Premier Support have suggested recreating the full-text catalog on
the
> table. Which has been done.
> 7. They also requested the full-text service being run under a domain
level
> user account instead of localsystem. That has also been done.
>
> Any additional information can be provided, and any help would be very
much
> appreciated.
>
> Thanks
> Mark
>
>
| |
| Mark Pope 2004-04-23, 8:36 am |
| Thanks for the reply. Unfortunately due to lack of commercial benefits we
are unable to upgrade to CS2002.
Can you suggest any patches or workarounds that will have the same effect. I
can confirm that deleting the full-text catalog stops the timeouts occurring
but unfortunately this also restricts vital functionality on site.
Thanks
Mark
"Vinayak Tadas [MS]" <vtadas@online.microsoft.com> wrote in message
news:%238KTNdKKEHA.1892@TK2MSFTNGP09.phx.gbl...
> At the end of the import process the CatalogManager.ImportXml method
> refreshes the full text indexes. As you figured out this is causing the
> locks.
> I am not sure if this will help you but in CS2002 we added a parameter on
> the ImportXml which will turn off generating the fulltext indexes thereby
> skipping the last step of the import.
>
> Thanks
> Vinayak Tadas
> Microsoft
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> You assume all risk for your use. © 2002 Microsoft Corporation. All rights
> reserved.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> Get Secure! For more info visit http://www.microsoft.com/security.
Please
> reply to the newsgroups only. Thanks
>
>
>
>
> "Mark Pope" <MPope@datamonitor.com> wrote in message
> news:e0WyEHKKEHA.204@TK2MSFTNGP10.phx.gbl...
> experience
> the
the[vbcol=seagreen]
> the
> level
> much
>
>
| |
| Max Akbar 2004-04-28, 12:34 am |
| Run profiler and see if you are full text index is full population or
incremental if full population then there isn't much that you can do short
of modifying the stored procedure. If it's incremental population then for
all the tables that have the Full Text enabled make sure that you have
timestamp field and that should fix your issues.
Good luck,
-Max
"Mark Pope" <MPope@datamonitor.com> wrote in message
news:Ov1PJySKEHA.1644@TK2MSFTNGP09.phx.gbl...
> Thanks for the reply. Unfortunately due to lack of commercial benefits we
> are unable to upgrade to CS2002.
>
> Can you suggest any patches or workarounds that will have the same effect.
> I
> can confirm that deleting the full-text catalog stops the timeouts
> occurring
> but unfortunately this also restricts vital functionality on site.
>
> Thanks
> Mark
>
> "Vinayak Tadas [MS]" <vtadas@online.microsoft.com> wrote in message
> news:%238KTNdKKEHA.1892@TK2MSFTNGP09.phx.gbl...
> rights.
> Please
> the
>
>
|
|
|
|