Engelbert
Tue Apr 11 10:51:17 CDT 2006
Well that explains the search problem <grin>, I'm glad I asked.
This is the WSS FAQ item
http://www.asaris.de/sites/walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=205
It was written quite a while ago so in fact today you would tend not to do
it via the command line (first option) but just select web farm when
installing (second option).
As I wrote earlier "web farm" just means SQL Server installation it does not
mean you have to have more than one server (although most people naturally
interpret it in that way - you are by no means alone!)
[Talk about confusing options]
Good luck. It should go smoothly if you select the right option. Read the
Admin Guide (there's a link to that in the MS Articles (Downloads section)
section of the WSS FAQ site if you can't find it (or don't want to look) on
the Microsoft site) to see how to connect to SQL Server when the question
comes during the install.
Engelbert
"miket00" <miket00@discussions.microsoft.com> wrote in message
news:B8DCE5EE-9FF8-4486-A6C3-7DE66D7B73D3@microsoft.com...
> Yes, WSS is installed on a single server using the default install. How
> can
> I change the install so it will utilize SQL instead of WMSDE? I will get
> all
> of these acronyms straight someday!
>
> Thank you!
> Mike
>
> "Engelbert" wrote:
>
>> I'm curious about this
>>
>> >The database is installed as a single instance in IIS and is not
>> >installed
>> >as a farm. Should it be installed as a farm? If so, is there a way to
>> >either migrate this installation, or do we need to do a new install with
>> >a
>> >restore from a sharepoint backup? Are these issues related to the IIS
>> >database being installed as a single install instead of as a farm, or is
>> >this
>> >a characteristic that is inherent to setting up this type of
>> >configuration
>> >of
>> >WSS and SQL?
>>
>> Can you confirm that all you mean by the above is that you installed WSS
>> on
>> a single server ?
>>
>> If you when installing specified the default install and not as a "web
>> farm"
>> then irrespective of whether you have SQL Server installed on that
>> server,
>> you will have in fact installed WSS to use WMSDE and thus will not have
>> search.
>>
>> [Note too that your subject is wrong - you do not have STS, you have WSS
>> as
>> shown by your text (STS is a different product)]
>>
>> Engelbert
>>
>>
>> "miket00" <miket00@discussions.microsoft.com> wrote in message
>> news:FDA4AFA5-23DC-4473-886B-09DAD285A9AD@microsoft.com...
>> > 1. We cannot run maintenance plans and therefore we can not use SQL
>> > automated backups and maintenance tasks.
>> > 2. We can not use SQL Enterprise Manager over the network to connect
>> > to
>> > the
>> > database. If we install anything under the network parameters the site
>> > then
>> > refuses connections.
>> > 3. The search function in SharePoint is not working. The full text
>> > function is installed in SQL and the searh function button is checked.
>> > The database is installed as a single instance in IIS and is not
>> > installed
>> > as a farm. Should it be installed as a farm? If so, is there a way to
>> > either migrate this installation, or do we need to do a new install
>> > with a
>> > restore from a sharepoint backup? Are these issues related to the IIS
>> > database being installed as a single install instead of as a farm, or
>> > is
>> > this
>> > a characteristic that is inherent to setting up this type of
>> > configuration
>> > of
>> > WSS and SQL?
>> >
>> >
>>
>>
>>