Full text Substring search not working

I have Sql server 2005 SP2.
I enabled it for Full Text search. Substring search where i enter *word* doesn't return any row.
I have a table testtable where description has word Extinguisher.

If i run a query with *ting* it doesn't return any row.
select * from testtable where contains(description,'"*xting*"') ;

But it works if i do
select * from testtable where contains(description,'"Exting*"') ;

The Full text search document says it supports substring search.
Is it an issue with sql server 2005?Please help.SQL Server doesn't support leading wildcards. Therefore your first query will be searching on "xting*" explaining why no results are returned.

I'm not sure why MS does this. Perhaps request it for SQL2008!!

HTH.

|||Doign a short talk with a fellow MVP SimonS, this is due to the Wordbreakers which are language specified. They can only chop the words according to known word breaking settings. So it depends whether a compound word can be broken into multiple ones. Searching within the word is that case not possible, searching for the words within a compound is possible if the wordbreaker can identity the appropiate individual words.

Jens K. Suessmeyer

http://www.sqlserver2005.de

Full Text Indexing on Microsoft SQL Server 2000 with Windows XP Pro

I am wondering if FUll Text Indexing is suported with MS SQL Server 2000
Developer Edition on XP Pro SP2 . I have the service installed and setup. I
have created several catalogs with data but when they are done populating
they show up with an Item Count of 0 and a Unique Index of 1 despite the
fact that there are 10+ records with extremely different data in the 3
columns that are being indexed.
I am not seeing any unusual messages in the Event Viewer also. I have
uninstalled and reinstalled already and the Server is running under an
Administrator User
Hi,
Thanks for your post.
From your descriptions, I understood that you would like to know whether
Full-Text Search is support in SQL Server Dev Edition and how to implement
it. Have I understood you? Correct me if I was wrong.
Based on my scope, Full-Text Search is supported in SQL Server 2000 Dev
Edition on Windows XP Pro. See more deatiled descritption about this in the
following links
Features Supported by the Editions of SQL Server 2000
http://msdn.microsoft.com/library/de...us/architec/8_
ar_ts_1cdv.asp
For the second question, I am not sure your detailed steps on how to
implement the Full-Text Search for the Table, would you please give me more
detail information about doing so? Here is an sample doing this with SQL
Server Enterprise Manager.
1. enable a table for full-text indexing
- Expand Databases, expand the database in which the table belongs, and
then click Tables.
- In the details pane, right-click the table, click Full-Text Index Table,
and then click Define Full-Text Indexing on a Table.
2. To create a full-text catalog
- right-click the database where you want the full-text catalog.
- Click New, and then click New Full-Text Catalog.
- Complete the New Full-Text Catalog dialog box.
3. Make a Full Populating
- expand the database that contains the full-text catalog to rebuild.
- Click Full-Text Catalogs, and then right-click the specific catalog to
populate.
- Click Start Full Population
4. See whether the data had been updated
- right-click the specific catalog to review.
- Click Properties, and then click the Status, Tables, and Schedules tabs,
as appropriate.
See the following chapter in Books Online or MSDN Online for more detailed
information
Creating and Maintaining Databases -> Full-Text Indexes ->
Administering Full-Text Features Using SQL Enterprise Manager
Hope this helps and please feel free to let me know whether it works or you
need furhter help. Thank you for your patience and corporation.
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Full Text Indexing on Microsoft SQL Server 2000 with Windows XP Pro

I am wondering if FUll Text Indexing is suported with MS SQL Server 2000
Developer Edition on XP Pro SP2 . I have the service installed and setup. I
have created several catalogs with data but when they are done populating
they show up with an Item Count of 0 and a Unique Index of 1 despite the
fact that there are 10+ records with extremely different data in the 3
columns that are being indexed.
I am not seeing any unusual messages in the Event Viewer also. I have
uninstalled and reinstalled already and the Server is running under an
Administrator UserHi,
Thanks for your post.
From your descriptions, I understood that you would like to know whether
Full-Text Search is support in SQL Server Dev Edition and how to implement
it. Have I understood you? Correct me if I was wrong.
Based on my scope, Full-Text Search is supported in SQL Server 2000 Dev
Edition on Windows XP Pro. See more deatiled descritption about this in the
following links
Features Supported by the Editions of SQL Server 2000
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
ar_ts_1cdv.asp
For the second question, I am not sure your detailed steps on how to
implement the Full-Text Search for the Table, would you please give me more
detail information about doing so? Here is an sample doing this with SQL
Server Enterprise Manager.
1. enable a table for full-text indexing
- Expand Databases, expand the database in which the table belongs, and
then click Tables.
- In the details pane, right-click the table, click Full-Text Index Table,
and then click Define Full-Text Indexing on a Table.
2. To create a full-text catalog
- right-click the database where you want the full-text catalog.
- Click New, and then click New Full-Text Catalog.
- Complete the New Full-Text Catalog dialog box.
3. Make a Full Populating
- expand the database that contains the full-text catalog to rebuild.
- Click Full-Text Catalogs, and then right-click the specific catalog to
populate.
- Click Start Full Population
4. See whether the data had been updated
- right-click the specific catalog to review.
- Click Properties, and then click the Status, Tables, and Schedules tabs,
as appropriate.
See the following chapter in Books Online or MSDN Online for more detailed
information
Creating and Maintaining Databases -> Full-Text Indexes ->
Administering Full-Text Features Using SQL Enterprise Manager
Hope this helps and please feel free to let me know whether it works or you
need furhter help. Thank you for your patience and corporation.
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I reposted the question in news:microsoft.public.sqlserver.programming and
received a reply from Mr. Kane who point dme to a KB that while completely
unrelated showed me where to find the Auditiong options for SQL Server which
I used to pinpoint the real problem. The problem has been resolved.
""Michael Cheng [MSFT]"" wrote:
> Hi,
> Thanks for your post.
> From your descriptions, I understood that you would like to know whether
> Full-Text Search is support in SQL Server Dev Edition and how to implement
> it. Have I understood you? Correct me if I was wrong.
> Based on my scope, Full-Text Search is supported in SQL Server 2000 Dev
> Edition on Windows XP Pro. See more deatiled descritption about this in the
> following links
> Features Supported by the Editions of SQL Server 2000
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
> ar_ts_1cdv.asp
> For the second question, I am not sure your detailed steps on how to
> implement the Full-Text Search for the Table, would you please give me more
> detail information about doing so? Here is an sample doing this with SQL
> Server Enterprise Manager.
> 1. enable a table for full-text indexing
> - Expand Databases, expand the database in which the table belongs, and
> then click Tables.
> - In the details pane, right-click the table, click Full-Text Index Table,
> and then click Define Full-Text Indexing on a Table.
> 2. To create a full-text catalog
> - right-click the database where you want the full-text catalog.
> - Click New, and then click New Full-Text Catalog.
> - Complete the New Full-Text Catalog dialog box.
> 3. Make a Full Populating
> - expand the database that contains the full-text catalog to rebuild.
> - Click Full-Text Catalogs, and then right-click the specific catalog to
> populate.
> - Click Start Full Population
> 4. See whether the data had been updated
> - right-click the specific catalog to review.
> - Click Properties, and then click the Status, Tables, and Schedules tabs,
> as appropriate.
> See the following chapter in Books Online or MSDN Online for more detailed
> information
> Creating and Maintaining Databases -> Full-Text Indexes ->
> Administering Full-Text Features Using SQL Enterprise Manager
> Hope this helps and please feel free to let me know whether it works or you
> need furhter help. Thank you for your patience and corporation.
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>|||Hi,
I have noticed that thread, it's great to hear that it was resolved and
thanks for letting me know about that:)
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Full Text Indexing on Microsoft SQL Server 2000 with Windows XP Pro

I am wondering if FUll Text Indexing is suported with MS SQL Server 2000
Developer Edition on XP Pro SP2 . I have the service installed and setup. I
have created several catalogs with data but when they are done populating
they show up with an Item Count of 0 and a Unique Index of 1 despite the
fact that there are 10+ records with extremely different data in the 3
columns that are being indexed.
I am not seeing any unusual messages in the Event Viewer also. I have
uninstalled and reinstalled already and the Server is running under an
Administrator UserHi,
Thanks for your post.
From your descriptions, I understood that you would like to know whether
Full-Text Search is support in SQL Server Dev Edition and how to implement
it. Have I understood you? Correct me if I was wrong.
Based on my scope, Full-Text Search is supported in SQL Server 2000 Dev
Edition on Windows XP Pro. See more deatiled descritption about this in the
following links
Features Supported by the Editions of SQL Server 2000
http://msdn.microsoft.com/library/d...-us/architec/8_
ar_ts_1cdv.asp
For the second question, I am not sure your detailed steps on how to
implement the Full-Text Search for the Table, would you please give me more
detail information about doing so? Here is an sample doing this with SQL
Server Enterprise Manager.
1. enable a table for full-text indexing
- Expand Databases, expand the database in which the table belongs, and
then click Tables.
- In the details pane, right-click the table, click Full-Text Index Table,
and then click Define Full-Text Indexing on a Table.
2. To create a full-text catalog
- right-click the database where you want the full-text catalog.
- Click New, and then click New Full-Text Catalog.
- Complete the New Full-Text Catalog dialog box.
3. Make a Full Populating
- expand the database that contains the full-text catalog to rebuild.
- Click Full-Text Catalogs, and then right-click the specific catalog to
populate.
- Click Start Full Population
4. See whether the data had been updated
- right-click the specific catalog to review.
- Click Properties, and then click the Status, Tables, and Schedules tabs,
as appropriate.
See the following chapter in Books Online or MSDN Online for more detailed
information
Creating and Maintaining Databases -> Full-Text Indexes ->
Administering Full-Text Features Using SQL Enterprise Manager
Hope this helps and please feel free to let me know whether it works or you
need furhter help. Thank you for your patience and corporation.
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Full population very slow

I've got SQL2000 Enterprise edition running on windows 2000 advanced server,
we've recently upgraded from SQL sp2 to sp3a, this caused a catalog rebuild
but full population is taking forever. The column with Full text search
enabled is of image type, there are 2.5 million record in the table, about
7GB in size.
I've started full population 2 days ago and it's still showing "Population
in progress", when I view the property page of the catalog, I can see ~
2300000 items, catalog size: 190MB, unique key count: 362586. It appears to
be processing 1000 items per minute.
The server has 8 CPUs, 8GB RAM with /PAE and /3GB enabled, heavy duty SAN
disks.
mssdmn.exe is the most active process, it's using between 30-40 CPU on one
processor only, disk utilization is minimal and plenty of physical memory
available for use. This process is using 6 threads, 10MB RAM, mssearch.exe is
using 50MB RAM and 16 threads.
Is there any way of speeding up population?
Thanks,
Ad
set sp_fulltext_service 'resource_usage', 5
"Ad" <Ad@.discussions.microsoft.com> wrote in message
news:B94E0F3A-7655-4D8A-8605-EA1BC43E6329@.microsoft.com...
> I've got SQL2000 Enterprise edition running on windows 2000 advanced
> server,
> we've recently upgraded from SQL sp2 to sp3a, this caused a catalog
> rebuild
> but full population is taking forever. The column with Full text search
> enabled is of image type, there are 2.5 million record in the table, about
> 7GB in size.
> I've started full population 2 days ago and it's still showing "Population
> in progress", when I view the property page of the catalog, I can see ~
> 2300000 items, catalog size: 190MB, unique key count: 362586. It appears
> to
> be processing 1000 items per minute.
> The server has 8 CPUs, 8GB RAM with /PAE and /3GB enabled, heavy duty SAN
> disks.
> mssdmn.exe is the most active process, it's using between 30-40 CPU on one
> processor only, disk utilization is minimal and plenty of physical memory
> available for use. This process is using 6 threads, 10MB RAM, mssearch.exe
> is
> using 50MB RAM and 16 threads.
> Is there any way of speeding up population?
> Thanks,
> Ad
>
|||Ad,
There are a couple of thing you can do to improve the FT Indexing
performance without stopping & re-locating the FT Catalog. You can set the
MSSearch service's to use one CPU and then use sp_configure to set the
affinity of SQL Server to that cpu to avoid cpu contention during heavy
MSSearch CPU usage via the following method - launch the Tskmgr.exe from the
AT command on the multi-proc server where sql server resides, as follows:
at <current_time+1min> /interactive taskmgr.exe
when it launches, you can then set "cpu affinity" for the MSSearch service
to a cpu or set of cpu's not being used by SQL Server. Then you would use
sp_configure to set SQL Server's cpu affinity to the other cpu's, thus
preventing the cpu usage of mssearch from affecting your sql server
processing. Note, this only works on multi-processor servers and is a
secured method for achieving this feature.
Additionally, as your server has lots of RAM, you can use
sp_fulltext_service 'resource_usage', 5 to set the MSSearch service to 5
(dedicated), and it will use the max amount of RAM (512Mb), but only if the
RAM is not being used by either the OS or by SQL Server.
Finally, I'd highly recommend that you review all the resources "SQL Server
2000 Full-Text Search Resources and Links" at:
http://spaces.msn.com/members/jtkane/Blog/cns!1pWDBCiDX1uvH5ATJmNCVLPQ!305.entry
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Ad" <Ad@.discussions.microsoft.com> wrote in message
news:B94E0F3A-7655-4D8A-8605-EA1BC43E6329@.microsoft.com...
> I've got SQL2000 Enterprise edition running on windows 2000 advanced
server,
> we've recently upgraded from SQL sp2 to sp3a, this caused a catalog
rebuild
> but full population is taking forever. The column with Full text search
> enabled is of image type, there are 2.5 million record in the table, about
> 7GB in size.
> I've started full population 2 days ago and it's still showing
"Population
> in progress", when I view the property page of the catalog, I can see ~
> 2300000 items, catalog size: 190MB, unique key count: 362586. It appears
to
> be processing 1000 items per minute.
> The server has 8 CPUs, 8GB RAM with /PAE and /3GB enabled, heavy duty SAN
> disks.
> mssdmn.exe is the most active process, it's using between 30-40 CPU on one
> processor only, disk utilization is minimal and plenty of physical memory
> available for use. This process is using 6 threads, 10MB RAM, mssearch.exe
is
> using 50MB RAM and 16 threads.
> Is there any way of speeding up population?
> Thanks,
> Ad
>
|||sp_fulltext_service 'resource_usage', 5 , did not make any difference, does
it need stop and re-start of MSSearch service?
Thanks,
Ad
|||Ad,
I didn't think it would make much difference. However, where you get the
biggest bang for your buck, is ensuring that the FT Catalog is on a separate
disk drive from your database files. Can you stop the Full Population, drop
and re-create the FT Catalog on separate disk array or better yet, on a
separate disk controller? See SQL 2000 BOL title "Full-text Search
Recommendations" for more info on this.
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Ad" <Ad@.discussions.microsoft.com> wrote in message
news:B72E38AF-4FFF-4F60-9F84-BF56213AC220@.microsoft.com...
> sp_fulltext_service 'resource_usage', 5 , did not make any difference,
does
> it need stop and re-start of MSSearch service?
> Thanks,
> Ad
>
>
|||The FT Catalog is on a dedicated SAN disk which is almost idle, in fact the
whole disk is cached. So there are plenty of resources on the server that FT
can't utilize, this leads me to believe FT has scalability issues.
Regards,
Ad
"John Kane" wrote:

> Ad,
> I didn't think it would make much difference. However, where you get the
> biggest bang for your buck, is ensuring that the FT Catalog is on a separate
> disk drive from your database files. Can you stop the Full Population, drop
> and re-create the FT Catalog on separate disk array or better yet, on a
> separate disk controller? See SQL 2000 BOL title "Full-text Search
> Recommendations" for more info on this.
> Regards,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "Ad" <Ad@.discussions.microsoft.com> wrote in message
> news:B72E38AF-4FFF-4F60-9F84-BF56213AC220@.microsoft.com...
> does
>
>

Full Install for SP2

I have one production SQL server 2000 with Reporting services SP2 installed
on it. I have a redundent IIS 6.0 just purchased. I went to install RS on
it and point it to the production machine but it won't install because the CD
I have is RS SP1 which isn't compatible with SP2. How can I get my hands on
a Full install of RS SP2 so that I can install it on my new IIS machine?
Thanks,
JohnThere is not a full install with SP2. You have to install and then upgrade
with SP2. SP2 includes all the fixes from SP1.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"John Supplee" <JohnSupplee@.discussions.microsoft.com> wrote in message
news:D8929F90-02FE-4782-AECF-E3028CC5C72F@.microsoft.com...
>I have one production SQL server 2000 with Reporting services SP2 installed
> on it. I have a redundent IIS 6.0 just purchased. I went to install RS
> on
> it and point it to the production machine but it won't install because the
> CD
> I have is RS SP1 which isn't compatible with SP2. How can I get my hands
> on
> a Full install of RS SP2 so that I can install it on my new IIS machine?
> Thanks,
> John
>|||Bruce,
Thanks for your reply. I already have SP2 installed. I am trying to
install Reporting Services on a new IIS machine and it won't let me because I
have a RS SP1 install and that is not compatible with SP2. Are you telling
me the only way to install this on my new machine is to completely uninstall
RS, on my production machine, and then reinstall RS on the new IIS machine?
Do you know if MS is going to come out with a CD soon for a full RS SP2
install? Since SP2 is incompatible with SP1 I can't imagine I'll be the only
one with this problem...
Thanks,
John
"Bruce L-C [MVP]" wrote:
> There is not a full install with SP2. You have to install and then upgrade
> with SP2. SP2 includes all the fixes from SP1.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "John Supplee" <JohnSupplee@.discussions.microsoft.com> wrote in message
> news:D8929F90-02FE-4782-AECF-E3028CC5C72F@.microsoft.com...
> >I have one production SQL server 2000 with Reporting services SP2 installed
> > on it. I have a redundent IIS 6.0 just purchased. I went to install RS
> > on
> > it and point it to the production machine but it won't install because the
> > CD
> > I have is RS SP1 which isn't compatible with SP2. How can I get my hands
> > on
> > a Full install of RS SP2 so that I can install it on my new IIS machine?
> > Thanks,
> > John
> >
>
>|||I'm confused on what you are trying to do. Are you setting up up a web farm?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"John Supplee" <JohnSupplee@.discussions.microsoft.com> wrote in message
news:DB20322D-8C67-43A0-B520-24BF7E80C34B@.microsoft.com...
> Bruce,
> Thanks for your reply. I already have SP2 installed. I am trying to
> install Reporting Services on a new IIS machine and it won't let me
> because I
> have a RS SP1 install and that is not compatible with SP2. Are you
> telling
> me the only way to install this on my new machine is to completely
> uninstall
> RS, on my production machine, and then reinstall RS on the new IIS
> machine?
> Do you know if MS is going to come out with a CD soon for a full RS SP2
> install? Since SP2 is incompatible with SP1 I can't imagine I'll be the
> only
> one with this problem...
> Thanks,
> John
> "Bruce L-C [MVP]" wrote:
>> There is not a full install with SP2. You have to install and then
>> upgrade
>> with SP2. SP2 includes all the fixes from SP1.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "John Supplee" <JohnSupplee@.discussions.microsoft.com> wrote in message
>> news:D8929F90-02FE-4782-AECF-E3028CC5C72F@.microsoft.com...
>> >I have one production SQL server 2000 with Reporting services SP2
>> >installed
>> > on it. I have a redundent IIS 6.0 just purchased. I went to install
>> > RS
>> > on
>> > it and point it to the production machine but it won't install because
>> > the
>> > CD
>> > I have is RS SP1 which isn't compatible with SP2. How can I get my
>> > hands
>> > on
>> > a Full install of RS SP2 so that I can install it on my new IIS
>> > machine?
>> > Thanks,
>> > John
>> >
>>|||I am setting up redundancy. I have a production IIS and SQL server running
RS SP2. I have a redundant SQL server that is getting updates from the
production server using Double-take. I would like to have the production IIS
machine replicate to the backup IIS machine using the same software. In
order to do this I need all the same products and versions on the redundant
server before I set up the replication. Unfortunately I upgraded my
production IIS and SQL to SP2 before I did the original install of RS on my
backup IIS machine. I tried installing RS but it tells me my CD RS version,
SP1, is incompatible with the production SQL version, SP2. I figured it
would be easy enough to just get a CD with a full install, including SP2,
from MS.
"Bruce L-C [MVP]" wrote:
> I'm confused on what you are trying to do. Are you setting up up a web farm?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "John Supplee" <JohnSupplee@.discussions.microsoft.com> wrote in message
> news:DB20322D-8C67-43A0-B520-24BF7E80C34B@.microsoft.com...
> > Bruce,
> > Thanks for your reply. I already have SP2 installed. I am trying to
> > install Reporting Services on a new IIS machine and it won't let me
> > because I
> > have a RS SP1 install and that is not compatible with SP2. Are you
> > telling
> > me the only way to install this on my new machine is to completely
> > uninstall
> > RS, on my production machine, and then reinstall RS on the new IIS
> > machine?
> > Do you know if MS is going to come out with a CD soon for a full RS SP2
> > install? Since SP2 is incompatible with SP1 I can't imagine I'll be the
> > only
> > one with this problem...
> >
> > Thanks,
> > John
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> There is not a full install with SP2. You have to install and then
> >> upgrade
> >> with SP2. SP2 includes all the fixes from SP1.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "John Supplee" <JohnSupplee@.discussions.microsoft.com> wrote in message
> >> news:D8929F90-02FE-4782-AECF-E3028CC5C72F@.microsoft.com...
> >> >I have one production SQL server 2000 with Reporting services SP2
> >> >installed
> >> > on it. I have a redundent IIS 6.0 just purchased. I went to install
> >> > RS
> >> > on
> >> > it and point it to the production machine but it won't install because
> >> > the
> >> > CD
> >> > I have is RS SP1 which isn't compatible with SP2. How can I get my
> >> > hands
> >> > on
> >> > a Full install of RS SP2 so that I can install it on my new IIS
> >> > machine?
> >> > Thanks,
> >> > John
> >> >
> >>
> >>
> >>
>
>|||You might not be the only one but what you are doing is not the normal way
for redundancy (by normal I mean the way the product is designed to provide
redundancy). RS was designed to provide reduncancy by creating a web farm.
All the IIS boxes use the same, single database server (which could have a
redundancy setup). The downside of this is licensing, each box needs to have
an enterprise license. Although this might still be the case with what you
are doing as well. At a minimum today you need 2 licenses. One for your IIS
box and one for your SQL Server box.
I suggesting reading up on how to install and setup a web farm, could be it
would give you ideas on how to move ahead with this.
Off the top of my head one thing you could do is to temporarily have SQL
Server locally on the second box and install RS. Then when done point it
away from being local to the other SQL Server box and remove SQL Server from
the second IIS box. I know this is possible but have not done it myself.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"John Supplee" <JohnSupplee@.discussions.microsoft.com> wrote in message
news:CC7BDAC3-1F73-4848-A0E8-F190068C363B@.microsoft.com...
>I am setting up redundancy. I have a production IIS and SQL server running
> RS SP2. I have a redundant SQL server that is getting updates from the
> production server using Double-take. I would like to have the production
> IIS
> machine replicate to the backup IIS machine using the same software. In
> order to do this I need all the same products and versions on the
> redundant
> server before I set up the replication. Unfortunately I upgraded my
> production IIS and SQL to SP2 before I did the original install of RS on
> my
> backup IIS machine. I tried installing RS but it tells me my CD RS
> version,
> SP1, is incompatible with the production SQL version, SP2. I figured it
> would be easy enough to just get a CD with a full install, including SP2,
> from MS.
> "Bruce L-C [MVP]" wrote:
>> I'm confused on what you are trying to do. Are you setting up up a web
>> farm?
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "John Supplee" <JohnSupplee@.discussions.microsoft.com> wrote in message
>> news:DB20322D-8C67-43A0-B520-24BF7E80C34B@.microsoft.com...
>> > Bruce,
>> > Thanks for your reply. I already have SP2 installed. I am trying to
>> > install Reporting Services on a new IIS machine and it won't let me
>> > because I
>> > have a RS SP1 install and that is not compatible with SP2. Are you
>> > telling
>> > me the only way to install this on my new machine is to completely
>> > uninstall
>> > RS, on my production machine, and then reinstall RS on the new IIS
>> > machine?
>> > Do you know if MS is going to come out with a CD soon for a full RS SP2
>> > install? Since SP2 is incompatible with SP1 I can't imagine I'll be
>> > the
>> > only
>> > one with this problem...
>> >
>> > Thanks,
>> > John
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> There is not a full install with SP2. You have to install and then
>> >> upgrade
>> >> with SP2. SP2 includes all the fixes from SP1.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "John Supplee" <JohnSupplee@.discussions.microsoft.com> wrote in
>> >> message
>> >> news:D8929F90-02FE-4782-AECF-E3028CC5C72F@.microsoft.com...
>> >> >I have one production SQL server 2000 with Reporting services SP2
>> >> >installed
>> >> > on it. I have a redundent IIS 6.0 just purchased. I went to
>> >> > install
>> >> > RS
>> >> > on
>> >> > it and point it to the production machine but it won't install
>> >> > because
>> >> > the
>> >> > CD
>> >> > I have is RS SP1 which isn't compatible with SP2. How can I get my
>> >> > hands
>> >> > on
>> >> > a Full install of RS SP2 so that I can install it on my new IIS
>> >> > machine?
>> >> > Thanks,
>> >> > John
>> >> >
>> >>
>> >>
>> >>
>>

Full back ups and transaction logs

Running 2005 with sp2. It seems that when running a full back up set as a
maintenace plan the transaction logs are filling up and do not shrink back.
The database is set to FULL recovery. Can some please assist me thank youFull backup does not empty the log. Use BACKUP LOG for that. If you don't want to do log backups,
set the recovery model to simple.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Victoria Morrison" <VictoriaMorrison@.discussions.microsoft.com> wrote in message
news:844C7B8A-2E4D-46F0-A51B-CAD917959C64@.microsoft.com...
> Running 2005 with sp2. It seems that when running a full back up set as a
> maintenace plan the transaction logs are filling up and do not shrink back.
> The database is set to FULL recovery. Can some please assist me thank you|||A FULL backup does nothing to clear the transaction log in FULL recovery
mode. You need regular LOG backups for that to happen. Even a LOG backup
will not shrink the file, it only allows committed and backed up portions of
the log to be reused. If you are in FULL recovery mode and wish to reap the
benefits of that you must do regular LOG backups, otherwise change the
recovery mode to Simple.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Victoria Morrison" <VictoriaMorrison@.discussions.microsoft.com> wrote in
message news:844C7B8A-2E4D-46F0-A51B-CAD917959C64@.microsoft.com...
> Running 2005 with sp2. It seems that when running a full back up set as a
> maintenace plan the transaction logs are filling up and do not shrink
> back.
> The database is set to FULL recovery. Can some please assist me thank
> you|||My questions is why would the back up cause the transaction log to grow and
grow. I do not recall this happending in 2000.
"Tibor Karaszi" wrote:
> Full backup does not empty the log. Use BACKUP LOG for that. If you don't want to do log backups,
> set the recovery model to simple.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Victoria Morrison" <VictoriaMorrison@.discussions.microsoft.com> wrote in message
> news:844C7B8A-2E4D-46F0-A51B-CAD917959C64@.microsoft.com...
> > Running 2005 with sp2. It seems that when running a full back up set as a
> > maintenace plan the transaction logs are filling up and do not shrink back.
> > The database is set to FULL recovery. Can some please assist me thank you
>|||The backup has nothing to do with the logs growing. It is the transactions
you are issuing that cause the log to grow and if you don't issue regular
Log backups this will keep happening. Something you may be encountering is
that even if you are in FULL recovery mode, until you issue a valid FULL
backup it will act as if it was in Simple mode and truncate the log when 70%
full. As soon as you issue a FULL backup it will expect you to also issue
regular Log backups. So I suspect no one ever did a FULL backup on the old
db.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Victoria Morrison" <VictoriaMorrison@.discussions.microsoft.com> wrote in
message news:4B79C133-8BFC-4841-B36D-FDD6482811E1@.microsoft.com...
> My questions is why would the back up cause the transaction log to grow
> and
> grow. I do not recall this happending in 2000.
> "Tibor Karaszi" wrote:
>> Full backup does not empty the log. Use BACKUP LOG for that. If you don't
>> want to do log backups,
>> set the recovery model to simple.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Victoria Morrison" <VictoriaMorrison@.discussions.microsoft.com> wrote in
>> message
>> news:844C7B8A-2E4D-46F0-A51B-CAD917959C64@.microsoft.com...
>> > Running 2005 with sp2. It seems that when running a full back up set
>> > as a
>> > maintenace plan the transaction logs are filling up and do not shrink
>> > back.
>> > The database is set to FULL recovery. Can some please assist me thank
>> > you