MSDE tools?

I have SQL Server 2000 but discovered it doesn't install on
Server 2003 Web Edition, so I installed MSDE 2000 revision
A.  Now I've googled up the wazoo, searched the SQL 2000
CD and searched the MS website but I can't figure out where
to get the tools to actually manage MSDE and set up a db and
what not.  Any pointers appreciated.  Thanks!

RobR  wrote:
> I have SQL Server 2000 but discovered it doesn't install on
> Server 2003 Web Edition, so I installed MSDE 2000 revision
> A.  Now I've googled up the wazoo, searched the SQL 2000
> CD and searched the MS website but I can't figure out where
> to get the tools to actually manage MSDE and set up a db and
> what not.  Any pointers appreciated.  Thanks!

http://www.microsoft.com/downloads/...&displaylang=en

--
David Gugick
Quest Software
www.imceda.com
www.quest.com

"RobR" <nospam@nospam.com> wrote in message
news:OEixeRJ9FHA.2716@TK2MSFTNGP11.phx.gbl...
>I have SQL Server 2000 but discovered it doesn't install on
> Server 2003 Web Edition, so I installed MSDE 2000 revision
> A.  Now I've googled up the wazoo, searched the SQL 2000
> CD and searched the MS website but I can't figure out where
> to get the tools to actually manage MSDE and set up a db and
> what not.  Any pointers appreciated.  Thanks!

If you have SQL Server 2000 then can you install the client tools? or
doesn't it let you?

IF it does let you install the client tools (and I don't know whether it
will) then you can use those to administer MSDE.
--
Brian Cryer
www.cryer.co.uk/brian

"David Gugick" <david.gugick-nospam@quest.com> wrote in message
news:%233$3A6K9FHA.2036@TK2MSFTNGP14.phx.gbl...
> RobR wrote: 
>
> http://www.microsoft.com/downloads/...&displaylang=en
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com

Thanks, but I was looking for windows client based tools.

"Brian Cryer" <brianc@127.0.0.1.activesol.co.uk> wrote in message
news:%23WsU5bN9FHA.2192@TK2MSFTNGP14.phx.gbl...
> "RobR" <nospam@nospam.com> wrote in message
> news:OEixeRJ9FHA.2716@TK2MSFTNGP11.phx.gbl... 
>
> If you have SQL Server 2000 then can you install the client tools? or
> doesn't it let you?
>
> IF it does let you install the client tools (and I don't know whether it
> will) then you can use those to administer MSDE.
> --
> Brian Cryer
> www.cryer.co.uk/brian
>
>

I couldn't figure out how to install them from the CD.  The install options
don't have an 'install client tools' option and there isn't a TOOLS or
SUPPORT directory on the CD.  I figured they're on there somewhere
and should be installable on almost any OS since people aren't
going to use the tools directly on the SQL server.

"RobR" <nospam@nospam.com> wrote in message
news:ul3BtjO9FHA.2036@TK2MSFTNGP14.phx.gbl...
>
> "Brian Cryer" <brianc@127.0.0.1.activesol.co.uk> wrote in message
> news:%23WsU5bN9FHA.2192@TK2MSFTNGP14.phx.gbl... 
>
> I couldn't figure out how to install them from the CD.  The install
> options
> don't have an 'install client tools' option and there isn't a TOOLS or
> SUPPORT directory on the CD.  I figured they're on there somewhere
> and should be installable on almost any OS since people aren't
> going to use the tools directly on the SQL server.

On my SQL Server 2000 cd, sticking it in the drive and letting it auto-run
... sorry, its actually quite a long way through the install screens before
it gives the option to install client tools. The route is to go as though
you were to install the full product and then you get to choose to just
install the client tools after a number of screens. I have a horrible
feeling that this is probably after its told you that it won't install on
your version of Windows.

Assuming it won't let you get that far, can you install the client tools on
another pc? You can install the tools on one pc and them administer a
database on another. If your 2003 web edition server is on a local network
then this shouldn't be a problem. If its remotely hosted then it will
require you to open the necessary ports in the protecting firewall - but I
have no idea which and if it were my hosted database I would be reluctant to
open any. Assuming it is a remotely hosted server (it might not be, you
didn't say) then you should still be able to set up a VPN connection between
your desktop pc and the remote host. Again there might be some firewall
configuration to worry about, but its probably more secure than opening the
necessary ports just for sql server.

I'm sure this isn't the way you want to go, but an alternative approach is
to script everything. Scripting is great if you might need to roll it out on
another server and need to know that you can reproduce the steps, but a pain
if you are just developing.

--
Brian Cryer
www.cryer.co.uk/brian

"Brian Cryer" <brianc@127.0.0.1.activesol.co.uk> wrote in message
news:NZGdnSnx1Iaa- RHenZ2dnUVZ8qqdnZ2d@
pipex.net...
> "RobR" <nospam@nospam.com> wrote in message
> news:ul3BtjO9FHA.2036@TK2MSFTNGP14.phx.gbl... 
>
> On my SQL Server 2000 cd, sticking it in the drive and letting it auto-run
> ... sorry, its actually quite a long way through the install screens
> before it gives the option to install client tools. The route is to go as
> though you were to install the full product and then you get to choose to
> just install the client tools after a number of screens. I have a horrible
> feeling that this is probably after its told you that it won't install on
> your version of Windows.
>
> Assuming it won't let you get that far, can you install the client tools
> on another pc? You can install the tools on one pc and them administer a
> database on another. If your 2003 web edition server is on a local network
> then this shouldn't be a problem. If its remotely hosted then it will
> require you to open the necessary ports in the protecting firewall - but I
> have no idea which and if it were my hosted database I would be reluctant
> to open any. Assuming it is a remotely hosted server (it might not be, you
> didn't say) then you should still be able to set up a VPN connection
> between your desktop pc and the remote host. Again there might be some
> firewall configuration to worry about, but its probably more secure than
> opening the necessary ports just for sql server.
>
> I'm sure this isn't the way you want to go, but an alternative approach is
> to script everything. Scripting is great if you might need to roll it out
> on another server and need to know that you can reproduce the steps, but a
> pain if you are just developing.
>
> --
> Brian Cryer
> www.cryer.co.uk/brian
>
>

thanks, i just came to reply i figured it out but you posted the
info i used.  you have to go through the motions as though
you were actually going to install SQL server.  i didn't expect
this to work since I was running on XP Pro.  I finally found
the info on installing the client tools in the help file on the CD.

RobR  wrote:
> thanks, i just came to reply i figured it out but you posted the
> info i used.  you have to go through the motions as though
> you were actually going to install SQL server.  i didn't expect
> this to work since I was running on XP Pro.  I finally found
> the info on installing the client tools in the help file on the CD.

If you want, you can install SQL Server 2000 directly on Windows XP
instead of using MSDE. The Personal Edition is automatically installed.

--
David Gugick
Quest Software
www.imceda.com
www.quest.com