We have a document management system made by some vendor. It relies
on a SQL database for storage. One table contains profile fields to
categorize the document, andother table contains the full text of the
document. this way people can search for documents by profile or by
ful-text content searching.

The problem is that when you search by profile fields ONLY, results
are returned pretty fast (spilt second) and when searching by full
text content ONLY, the search is also very fast. The problem is when
searching using both profile and full text content criteria.

We have been told that it could be a problem related to the index and
that reindexing the full text table or whatever (I'm not very good at
SQL) can fix the problem. The problem is that they've tried this
before and it didn't work and they're doing it again. It's been
reindexing for a day now and it's only 1/2 way done.

Is this normal when reindexing SQL tables?

It's been two days and it's still re-indexing! Is this normal?




On Sep 11, 2:33pm, Anubix <anu...@tampabay.rr.com> wrote:
> We have a document management system made by some vendor. It relies
> on a SQL database for storage. One table contains profile fields to
> categorize the document, andother table contains the full text of the
> document. this way people can search for documents by profile or by
> ful-text content searching.
>
> The problem is that when you search by profile fields ONLY, results
> are returned pretty fast (spilt second) and when searching by full
> text content ONLY, the search is also very fast. The problem is when
> searching using both profile and full text content criteria.
>
> We have been told that it could be a problem related to the index and
> that reindexing the full text table or whatever (I'm not very good at
> SQL) can fix the problem. The problem is that they've tried this
> before and it didn't work and they're doing it again. It's been
> reindexing for a day now and it's only 1/2 way done.
>
> Is this normal when reindexing SQL tables?

What is the hardware like that SQL Server is running on?

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Anubix" <anubix@tampabay.rr.com> wrote in message
news:524b7174-a6fd-4d67-95e5-c2c9309c9c73@r66g2000hsg.googlegroups.com...
It's been two days and it's still re-indexing! Is this normal?




On Sep 11, 2:33 pm, Anubix <anu...@tampabay.rr.com> wrote:
> We have a document management system made by some vendor. It relies
> on a SQL database for storage. One table contains profile fields to
> categorize the document, andother table contains the full text of the
> document. this way people can search for documents by profile or by
> ful-text content searching.
>
> The problem is that when you search by profile fields ONLY, results
> are returned pretty fast (spilt second) and when searching by full
> text content ONLY, the search is also very fast. The problem is when
> searching using both profile and full text content criteria.
>
> We have been told that it could be a problem related to the index and
> that reindexing the full text table or whatever (I'm not very good at
> SQL) can fix the problem. The problem is that they've tried this
> before and it didn't work and they're doing it again. It's been
> reindexing for a day now and it's only 1/2 way done.
>
> Is this normal when reindexing SQL tables?

And also what is the size of the table/indexes and do you have any blocking going on?

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message
news:eMRFS%23QFJHA.1272@TK2MSFTNGP05.phx.gbl...
> What is the hardware like that SQL Server is running on?
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
>
> "Anubix" <anubix@tampabay.rr.com> wrote in message
> news:524b7174-a6fd-4d67-95e5-c2c9309c9c73@r66g2000hsg.googlegroups.com...
> It's been two days and it's still re-indexing! Is this normal?
>
>
>
>
> On Sep 11, 2:33 pm, Anubix <anu...@tampabay.rr.com> wrote:
>> We have a document management system made by some vendor. It relies
>> on a SQL database for storage. One table contains profile fields to
>> categorize the document, andother table contains the full text of the
>> document. this way people can search for documents by profile or by
>> ful-text content searching.
>>
>> The problem is that when you search by profile fields ONLY, results
>> are returned pretty fast (spilt second) and when searching by full
>> text content ONLY, the search is also very fast. The problem is when
>> searching using both profile and full text content criteria.
>>
>> We have been told that it could be a problem related to the index and
>> that reindexing the full text table or whatever (I'm not very good at
>> SQL) can fix the problem. The problem is that they've tried this
>> before and it didn't work and they're doing it again. It's been
>> reindexing for a day now and it's only 1/2 way done.
>>
>> Is this normal when reindexing SQL tables?
>

HP Proliant ML370 G4. Xeon 3.4GHz (4 CPUs), BIOS release date
11/09/2005. 2GB RAM. Windows Server 2003 Std edition SP2. C: drive
= 39GB total, 25 GB free. I'm sorry I don't know the size of tables
or indexes. What file types should I look for? There's a .REFX that
998MB and another .REFsometing that's 1.2GB.


Thanks for the .



On Sep 13, 4:50am, "Tibor Karaszi"
<tibor_please.no.email_kara...@hotmail.nomail.co m> wrote:
> And also what is the size of the table/indexes and do you have any blocking going on?
>
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
>
> "Andrew J. Kelly" <sqlmvpnooos...@shadhawk.com> wrote in messagenews:eMRFS%23QFJHA.1272@TK2MSFTNGP05.phx.gb l...
>
>
>
> > What is the hardware like that SQL Server is running on?
>
> > --
> > Andrew J. Kelly SQL MVP
> > Solid Quality Mentors
>
> > "Anubix" <anu...@tampabay.rr.com> wrote in message
> >news:524b7174-a6fd-4d67-95e5-c2c9309c9c73@r66g2000hsg.googlegroups.com....
> > It's been two days and it's still re-indexing! Is this normal?
>
> > On Sep 11, 2:33 pm, Anubix <anu...@tampabay.rr.com> wrote:
> >> We have a document management system made by some vendor. It relies
> >> on a SQL database for storage. One table contains profile fields to
> >> categorize the document, andother table contains the full text of the
> >> document. this way people can search for documents by profile or by
> >> ful-text content searching.
>
> >> The problem is that when you search by profile fields ONLY, results
> >> are returned pretty fast (spilt second) and when searching by full
> >> text content ONLY, the search is also very fast. The problem is when
> >> searching using both profile and full text content criteria.
>
> >> We have been told that it could be a problem related to the index and
> >> that reindexing the full text table or whatever (I'm not very good at
> >> SQL) can fix the problem. The problem is that they've tried this
> >> before and it didn't work and they're doing it again. It's been
> >> reindexing for a day now and it's only 1/2 way done.
>
> >> Is this normal when reindexing SQL tables?- Hide quoted text -
>
> - Show quoted text -

Are you reindexing a SQL Server index on a table or rebuilding the Full Text
Catalogs? I can tell you right now that 2GB is way too little memory for
SQL Server and FTS and if this is all happening on a single drive you are
asking for it to take a long time.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Anubix" <anubix@tampabay.rr.com> wrote in message
news:ec6fab88-90fc-4759-9a8c-6b4d4c05f27c@k7g2000hsd.googlegroups.com...
HP Proliant ML370 G4. Xeon 3.4GHz (4 CPUs), BIOS release date
11/09/2005. 2GB RAM. Windows Server 2003 Std edition SP2. C: drive
= 39GB total, 25 GB free. I'm sorry I don't know the size of tables
or indexes. What file types should I look for? There's a .REFX that
998MB and another .REFsometing that's 1.2GB.


Thanks for the .



On Sep 13, 4:50 am, "Tibor Karaszi"
<tibor_please.no.email_kara...@hotmail.nomail.co m> wrote:
> And also what is the size of the table/indexes and do you have any
> blocking going on?
>
> --
> Tibor Karaszi, SQL Server
> MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
>
> "Andrew J. Kelly" <sqlmvpnooos...@shadhawk.com> wrote in
> messagenews:eMRFS%23QFJHA.1272@TK2MSFTNGP05.phx.gb l...
>
>
>
> > What is the hardware like that SQL Server is running on?
>
> > --
> > Andrew J. Kelly SQL MVP
> > Solid Quality Mentors
>
> > "Anubix" <anu...@tampabay.rr.com> wrote in message
> >news:524b7174-a6fd-4d67-95e5-c2c9309c9c73@r66g2000hsg.googlegroups.com...
> > It's been two days and it's still re-indexing! Is this normal?
>
> > On Sep 11, 2:33 pm, Anubix <anu...@tampabay.rr.com> wrote:
> >> We have a document management system made by some vendor. It relies
> >> on a SQL database for storage. One table contains profile fields to
> >> categorize the document, andother table contains the full text of the
> >> document. this way people can search for documents by profile or by
> >> ful-text content searching.
>
> >> The problem is that when you search by profile fields ONLY, results
> >> are returned pretty fast (spilt second) and when searching by full
> >> text content ONLY, the search is also very fast. The problem is when
> >> searching using both profile and full text content criteria.
>
> >> We have been told that it could be a problem related to the index and
> >> that reindexing the full text table or whatever (I'm not very good at
> >> SQL) can fix the problem. The problem is that they've tried this
> >> before and it didn't work and they're doing it again. It's been
> >> reindexing for a day now and it's only 1/2 way done.
>
> >> Is this normal when reindexing SQL tables?- Hide quoted text -
>
> - Show quoted text -

I looked in the database and there are no catalogs, so it must be an
index. I'm not the person doing this work, but I thought I should
look into it because I'm the IT person answering all the users'
questions, you know, why is it so slow?"

I agree with the RAM problem. I was surprised when I saw that. I don't
usually go in the server for anything. I'm Level 1 support. I will
tell my admin. Maybe that's the whole problem. Any other ideas?
Thanks so much for caring.


On Sep 13, 9:03pm, "Andrew J. Kelly" <sqlmvpnooos...@shadhawk.com>
wrote:
> Are you reindexing a SQL Server index on a table or rebuilding the Full Text
> Catalogs? I can tell you right now that 2GB is way too little memory for
> SQL Server and FTS and if this is all happening on a single drive you are
> asking for it to take a long time.
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Anubix" <anu...@tampabay.rr.com> wrote in message
>
> news:ec6fab88-90fc-4759-9a8c-6b4d4c05f27c@k7g2000hsd.googlegroups.com...
> HP Proliant ML370 G4. Xeon 3.4GHz (4 CPUs), BIOS release date
> 11/09/2005. 2GB RAM. Windows Server 2003 Std edition SP2. C: drive
> = 39GB total, 25 GB free. I'm sorry I don't know the size of tables
> or indexes. What file types should I look for? There's a .REFX that
> 998MB and another .REFsometing that's 1.2GB.
>
> Thanks for the .
>
> On Sep 13, 4:50 am, "Tibor Karaszi"
>
>

My guess is the entire server is underpowered for what you are trying to do.
Having so little memory and only a single drive will certainly slow down a
large index build. But as Tibor suggested you may have blocking issues as
well. Bottom line is that you need to narrow down the real bottleneck and it
sounds like you don't have the experience with SQL Server to do so. A such I
might suggest a consultant who does.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Anubix" <anubix@tampabay.rr.com> wrote in message
news:5b56250e-a29a-4af8-afb5-3ec044887f78@25g2000hsx.googlegroups.com...
I looked in the database and there are no catalogs, so it must be an
index. I'm not the person doing this work, but I thought I should
look into it because I'm the IT person answering all the users'
questions, you know, why is it so slow?"

I agree with the RAM problem. I was surprised when I saw that. I don't
usually go in the server for anything. I'm Level 1 support. I will
tell my admin. Maybe that's the whole problem. Any other ideas?
Thanks so much for caring.


On Sep 13, 9:03 pm, "Andrew J. Kelly" <sqlmvpnooos...@shadhawk.com>
wrote:
> Are you reindexing a SQL Server index on a table or rebuilding the Full
> Text
> Catalogs? I can tell you right now that 2GB is way too little memory for
> SQL Server and FTS and if this is all happening on a single drive you are
> asking for it to take a long time.
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Anubix" <anu...@tampabay.rr.com> wrote in message
>
> news:ec6fab88-90fc-4759-9a8c-6b4d4c05f27c@k7g2000hsd.googlegroups.com...
> HP Proliant ML370 G4. Xeon 3.4GHz (4 CPUs), BIOS release date
> 11/09/2005. 2GB RAM. Windows Server 2003 Std edition SP2. C: drive
> = 39GB total, 25 GB free. I'm sorry I don't know the size of tables
> or indexes. What file types should I look for? There's a .REFX that
> 998MB and another .REFsometing that's 1.2GB.
>
> Thanks for the .
>
> On Sep 13, 4:50 am, "Tibor Karaszi"
>
>

Thank you both for the information. You are correct in that I don't
have SQL experience. But now I have a little ammo to go to my boss
and request this issue be researched further. we're just going by
what the vendor says and maybe a consultant can figure out if the
product is just badly designed or if we can it by adding more RAM
or what. Thanks. Thread closed.


On Sep 14, 6:51pm, "Andrew J. Kelly" <sqlmvpnooos...@shadhawk.com>
wrote:
> My guess is the entire server is underpowered for what you are trying to do.
> Having so little memory and only a single drive will certainly slow down a
> large index build. But as Tibor suggested you may have blocking issues as
> well. Bottom line is that you need to narrow down the real bottleneck andit
> sounds like you don't have the experience with SQL Server to do so. A such I
> might suggest a consultant who does.
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Anubix" <anu...@tampabay.rr.com> wrote in message
>
> news:5b56250e-a29a-4af8-afb5-3ec044887f78@25g2000hsx.googlegroups.com...
> I looked in the database and there are no catalogs, so it must be an
> index. I'm not the person doing this work, but I thought I should
> look into it because I'm the IT person answering all the users'
> questions, you know, why is it so slow?"
>
> I agree with the RAM problem. I was surprised when I saw that. I don't
> usually go in the server for anything. I'm Level 1 support. I will
> tell my admin. Maybe that's the whole problem. Any other ideas?
> Thanks so much for caring.
>
> On Sep 13, 9:03 pm, "Andrew J. Kelly" <sqlmvpnooos...@shadhawk.com>
> wrote:
>
>
>
> > Are you reindexing a SQL Server index on a table or rebuilding the Full
> > Text
> > Catalogs? I can tell you right now that 2GB is way too little memory for
> > SQL Server and FTS and if this is all happening on a single drive you are
> > asking for it to take a long time.
>
> > --
> > Andrew J. Kelly SQL MVP
> > Solid Quality Mentors
>
> > "Anubix" <anu...@tampabay.rr.com> wrote in message
>
> >news:ec6fab88-90fc-4759-9a8c-6b4d4c05f27c@k7g2000hsd.googlegroups.com...
> > HP Proliant ML370 G4. Xeon 3.4GHz (4 CPUs), BIOS release date
> > 11/09/2005. 2GB RAM. Windows Server 2003 Std edition SP2. C: drive
> > = 39GB total, 25 GB free. I'm sorry I don't know the size of tables
> > or indexes. What file types should I look for? There's a .REFX that
> > 998MB and another .REFsometing that's 1.2GB.
>
> > Thanks for the .
>
> > On Sep 13, 4:50 am, "Tibor Karaszi"- Hide quoted text -
>
> - Show quoted text -