MSDE 2000

Did anybody tried to use this as a database server? Is there an administration interface somewhere which is free?

DennisI have used it as server. Basically it is a little brother of MSSQL. If you need you can later go over to MSSQL without any changes to database code. You can administer it using DbaMgr2k. This tool is free and you can do almost everything with it.|||Also be sure to check out the pinned post at the top of this forum to learn about SQL Web Data Administrator.

Terri

MSDE (yes I know this is the wrong group)

I have asked this in the MSDE group and had no replies, so I wondered if, as
it's basically SQL qithout the interface and with limits), whether you
knowledgeable people could answer this for me.
Is there any problems (operationally wise, or conflict wise) with putting
MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
server also has Exchange 2000 and ISA 2000 installed on it)?
I can obviously restrict the memory it can use so that's not a problem, but
I wondered if it would create problems or serious performance issues for the
DC.
Also, if it is OK to install on a DC, is the installation straightforward or
are there any special switches or settings I should use? Or do I just do a
plain install as I would on any machine?
Thanks
KeithIt is not a problem to install it on the DC. There is no difference in
instalation.
Generally it is not recommended because of the Microsoft's concept: one
server - one machine, but there are no problems with that.
Bojidar Alexandrov
"Keith" <@..> wrote in message news:uJZ0UXQLEHA.1484@.tk2msftngp13.phx.gbl...
> I have asked this in the MSDE group and had no replies, so I wondered if,
as
> it's basically SQL qithout the interface and with limits), whether you
> knowledgeable people could answer this for me.
> Is there any problems (operationally wise, or conflict wise) with putting
> MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
> server also has Exchange 2000 and ISA 2000 installed on it)?
> I can obviously restrict the memory it can use so that's not a problem,
but
> I wondered if it would create problems or serious performance issues for
the
> DC.
> Also, if it is OK to install on a DC, is the installation straightforward
or
> are there any special switches or settings I should use? Or do I just do
a
> plain install as I would on any machine?
> Thanks
> Keith
>|||I'd agree with that although I havent needed to do it
Simon|||Keith,
I posted a reply today, where I pointed out a potential issue with your serv
ice account.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Keith" <@..> wrote in message news:uJZ0UXQLEHA.1484@.tk2msftngp13.phx.gbl...
> I have asked this in the MSDE group and had no replies, so I wondered if,
as
> it's basically SQL qithout the interface and with limits), whether you
> knowledgeable people could answer this for me.
> Is there any problems (operationally wise, or conflict wise) with putting
> MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
> server also has Exchange 2000 and ISA 2000 installed on it)?
> I can obviously restrict the memory it can use so that's not a problem, bu
t
> I wondered if it would create problems or serious performance issues for t
he
> DC.
> Also, if it is OK to install on a DC, is the installation straightforward
or
> are there any special switches or settings I should use? Or do I just do
a
> plain install as I would on any machine?
> Thanks
> Keith
>

MSDE (yes I know this is the wrong group)

I have asked this in the MSDE group and had no replies, so I wondered if, as
it's basically SQL qithout the interface and with limits), whether you
knowledgeable people could answer this for me.
Is there any problems (operationally wise, or conflict wise) with putting
MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
server also has Exchange 2000 and ISA 2000 installed on it)?
I can obviously restrict the memory it can use so that's not a problem, but
I wondered if it would create problems or serious performance issues for the
DC.
Also, if it is OK to install on a DC, is the installation straightforward or
are there any special switches or settings I should use? Or do I just do a
plain install as I would on any machine?
Thanks
Keith
It is not a problem to install it on the DC. There is no difference in
instalation.
Generally it is not recommended because of the Microsoft's concept: one
server - one machine, but there are no problems with that.
Bojidar Alexandrov
"Keith" <@..> wrote in message news:uJZ0UXQLEHA.1484@.tk2msftngp13.phx.gbl...
> I have asked this in the MSDE group and had no replies, so I wondered if,
as
> it's basically SQL qithout the interface and with limits), whether you
> knowledgeable people could answer this for me.
> Is there any problems (operationally wise, or conflict wise) with putting
> MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
> server also has Exchange 2000 and ISA 2000 installed on it)?
> I can obviously restrict the memory it can use so that's not a problem,
but
> I wondered if it would create problems or serious performance issues for
the
> DC.
> Also, if it is OK to install on a DC, is the installation straightforward
or
> are there any special switches or settings I should use? Or do I just do
a
> plain install as I would on any machine?
> Thanks
> Keith
>
|||I'd agree with that although I havent needed to do it
Simon
|||Keith,
I posted a reply today, where I pointed out a potential issue with your service account.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Keith" <@..> wrote in message news:uJZ0UXQLEHA.1484@.tk2msftngp13.phx.gbl...
> I have asked this in the MSDE group and had no replies, so I wondered if, as
> it's basically SQL qithout the interface and with limits), whether you
> knowledgeable people could answer this for me.
> Is there any problems (operationally wise, or conflict wise) with putting
> MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
> server also has Exchange 2000 and ISA 2000 installed on it)?
> I can obviously restrict the memory it can use so that's not a problem, but
> I wondered if it would create problems or serious performance issues for the
> DC.
> Also, if it is OK to install on a DC, is the installation straightforward or
> are there any special switches or settings I should use? Or do I just do a
> plain install as I would on any machine?
> Thanks
> Keith
>

MSDE (yes I know this is the wrong group)

I have asked this in the MSDE group and had no replies, so I wondered if, as
it's basically SQL qithout the interface and with limits), whether you
knowledgeable people could answer this for me.
Is there any problems (operationally wise, or conflict wise) with putting
MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
server also has Exchange 2000 and ISA 2000 installed on it)?
I can obviously restrict the memory it can use so that's not a problem, but
I wondered if it would create problems or serious performance issues for the
DC.
Also, if it is OK to install on a DC, is the installation straightforward or
are there any special switches or settings I should use? Or do I just do a
plain install as I would on any machine?
Thanks
KeithIt is not a problem to install it on the DC. There is no difference in
instalation.
Generally it is not recommended because of the Microsoft's concept: one
server - one machine, but there are no problems with that.
Bojidar Alexandrov
"Keith" <@..> wrote in message news:uJZ0UXQLEHA.1484@.tk2msftngp13.phx.gbl...
> I have asked this in the MSDE group and had no replies, so I wondered if,
as
> it's basically SQL qithout the interface and with limits), whether you
> knowledgeable people could answer this for me.
> Is there any problems (operationally wise, or conflict wise) with putting
> MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
> server also has Exchange 2000 and ISA 2000 installed on it)?
> I can obviously restrict the memory it can use so that's not a problem,
but
> I wondered if it would create problems or serious performance issues for
the
> DC.
> Also, if it is OK to install on a DC, is the installation straightforward
or
> are there any special switches or settings I should use? Or do I just do
a
> plain install as I would on any machine?
> Thanks
> Keith
>|||I'd agree with that although I havent needed to do it
Simon|||Keith,
I posted a reply today, where I pointed out a potential issue with your service account.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Keith" <@..> wrote in message news:uJZ0UXQLEHA.1484@.tk2msftngp13.phx.gbl...
> I have asked this in the MSDE group and had no replies, so I wondered if, as
> it's basically SQL qithout the interface and with limits), whether you
> knowledgeable people could answer this for me.
> Is there any problems (operationally wise, or conflict wise) with putting
> MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
> server also has Exchange 2000 and ISA 2000 installed on it)?
> I can obviously restrict the memory it can use so that's not a problem, but
> I wondered if it would create problems or serious performance issues for the
> DC.
> Also, if it is OK to install on a DC, is the installation straightforward or
> are there any special switches or settings I should use? Or do I just do a
> plain install as I would on any machine?
> Thanks
> Keith
>