Force client components using a commmand line installation to diffrent location

Is it possible to force the SLQ 2005 Client Components to be installed into a diffrent location other than the default location?

What I'm trying to do is run the setup command though the command line to create an unattended client installation with all the client componets to a diffrent location that

Thanks, Any information or examples would be great!

There is a way to specify client component location is setup or on the command line but it can only be used for the first time SQL Server 2005 is installed on a machine. Once there is any product or instance of SQL Server 2005 on the machine this location cannot be changed. To specify the location on the command line you can use INSTALLSQLSHAREDDIR.

Note: there are still some components going under Program Files\Microsoft SQL Server\90 which location cannot be changed. But most of the client components is installed to INSTALLSQLSHAREDDIR.

For example:

setup.exe INSTALLSQLSHAREDDIR=D:\SQLTools ADDLOCAL=Client_Components,Connectivity,SQL_Tools90,SQL_WarehouseDevWorkbench /qb

ADDLOCAL lists all features you want to install. See template.ini in the same location as setup.exe for whole list of features.

FOR XML EXPLICIT output on MSDE?

Hello,
I have a problem with one of my SPs with a FOR XML EXPLICIT line. I tried it
on a SQL Server 2000 installation and it works fine.
Anyway, I've tried it with some of the MSDE GUIs (both standalone's and
WebServer Based) and it doesn't come up with the output. On the MSDE version
when I run it through the GUI Query Analyzer versions, it seems to run, it
spits out the non XML Select statements and it shows the "rows affected"
messages and it doesn't show any error messages.
Any idea what's happening?
Jeeves
Hi Jeeves,
It just sounds like the tools aren't rendering the XML output. That's
probably not that surprising. The MSDE won't be the problem. It does it just
fine so it will be ok with your apps.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jeeves De Veyra" <me@.jeevester.com> wrote in message
news:%23%23Dh6aDrEHA.2924@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have a problem with one of my SPs with a FOR XML EXPLICIT line. I tried
> it
> on a SQL Server 2000 installation and it works fine.
> Anyway, I've tried it with some of the MSDE GUIs (both standalone's and
> WebServer Based) and it doesn't come up with the output. On the MSDE
> version
> when I run it through the GUI Query Analyzer versions, it seems to run, it
> spits out the non XML Select statements and it shows the "rows affected"
> messages and it doesn't show any error messages.
> Any idea what's happening?
> Jeeves
>
|||Would you know of an MSDE tool that renders XML properly. I've been through
all of em and they give me zip... (waaahhhh!!!!)
Incidentally, I tried Microsofts Web based tool (the one that comes with
Cassini), how can the script timeouts be changed?
Jeeves
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:uxeJ29ErEHA.324@.TK2MSFTNGP11.phx.gbl...
> Hi Jeeves,
> It just sounds like the tools aren't rendering the XML output. That's
> probably not that surprising. The MSDE won't be the problem. It does it
just[vbcol=seagreen]
> fine so it will be ok with your apps.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Jeeves De Veyra" <me@.jeevester.com> wrote in message
> news:%23%23Dh6aDrEHA.2924@.TK2MSFTNGP12.phx.gbl...
tried[vbcol=seagreen]
it
>