MSDE to SQL Server

HI
Is it possible to upgrade SQL 2000 developer edition to SQL Serevr standered
edition
if so, how and what is the easist option
Thanks
bAccording to BOL, you can upgrade Developer Edition on SQL Server 2000 to
Enterprise Edition on SQL Server 2000/2005.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

MSDE to SQL Server

HI
Is it possible to upgrade SQL 2000 developer edition to SQL Serevr standered
edition
if so, how and what is the easist option
Thanks
bAccording to BOL, you can upgrade Developer Edition on SQL Server 2000 to
Enterprise Edition on SQL Server 2000/2005.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

MSDE Subscriber's database > 2GB

Hi all !
We have a database with publication on
SBS2003 Premium Edition,
and 4 subscribers on workstations in warehouses on:
- Windows XP Professional
- MSDE
The database is 1.6 GB now and growing
further. I should migrate from MSDE
to SQL Server 2000.
Which version of SQL has to be installed
at warehouses (on top of Win XP Prof)?
Do I have to break the replication before ?
Thanks,
Pagus
Paul,
what about Personal Edition + Win XP Pro ?
Win XP Pro is working OK with MSDE, I wouldn't like to
purchase Win Server product :-(
Pagus
On Mon, 6 Sep 2004 00:48:11 -0700, "Paul Ibison"
<Paul.Ibison@.Pygmalion.Com> wrote:

>Pagus,
>you'll need Standard or Enterprise Edition. The OSs=20
>required for these editions of sql server are:
>Windows Server 2003, Standard Edition1=20
>Windows Server 2003, Enterprise Edition1=20
>Windows Server 2003, Datacenter Edition1=20
>Windows=AE 2000 Server=20
>Windows 2000 Advanced Server=20
>Windows 2000 Datacenter Server=20
>Windows NT=AE Server version 4.0 with Service Pack 5 (SP5)=20
>or later=20
>Windows NT Server 4.0, Enterprise Edition, with SP5 or=20
>later=20
>HTH,
>Paul Ibison
>(The ONLY sql server 2000 replication book:
>http://www.nwsu.com/0974973602p.html)
>
|||Pagus,
you're quire right, subject to the following restrictions:
It includes a concurrent workload governor that limits
its scalability; performance degrades when more than five
Transact-SQL batches are executed concurrently.
It cannot act as a transactional replication publisher
(subscriber only).
Regards,
Paul Ibison

MSDE Seems to Install - Service Manager Loads - No Connection

Hi,
I uninstalled MSDE 2000 prior to installing SQL Server 2000 Developer
Edition. I then found I could not use Developer Edition with Visual Basic
..net Standard Edition and tried to reinstall MSDE. The installation seems
to go fine but when the Service Manager loads is tells me "Not Connected -
\\" no servers are in the Server drop-down and no services are listed in
the Services drop-down. I am very new to all of this and would very much
appreciate any help/advice you could offer. I have since uninstalled
Developer Edition to no avail. I am running Windows XP Pro.
Regards
Barry-Jon
hi Barry-Jon,
Microsoft wrote:
> Hi,
> I uninstalled MSDE 2000 prior to installing SQL Server 2000 Developer
> Edition. I then found I could not use Developer Edition with Visual
> Basic .net Standard Edition and tried to reinstall MSDE. The
> installation seems to go fine but when the Service Manager loads is
> tells me "Not Connected - \\" no servers are in the Server drop-down
> and no services are listed in the Services drop-down. I am very new
> to all of this and would very much appreciate any help/advice you
> could offer. I have since uninstalled Developer Edition to no avail.
> I am running Windows XP Pro.
> Regards
> Barry-Jon
please have a look at
http://support.microsoft.com/default...b;EN-US;814132 ...
you can modify this behaviour enabling the desired/required network protocol
by running the Server Network Utility (svrnetcn.exe)...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Microsoft" <barryjonoconnell_spam_no@.yahoo.co.uk> wrote in message
news:ucCLTwKEFHA.1188@.tk2msftngp13.phx.gbl...
> Hi,
> I uninstalled MSDE 2000 prior to installing SQL Server 2000 Developer
> Edition. I then found I could not use Developer Edition with Visual Basic
> .net Standard Edition and tried to reinstall MSDE. The installation seems
> to go fine but when the Service Manager loads is tells me "Not Connected -
> \\" no servers are in the Server drop-down and no services are listed in
> the Services drop-down. I am very new to all of this and would very much
> appreciate any help/advice you could offer. I have since uninstalled
> Developer Edition to no avail. I am running Windows XP Pro.
> Regards
> Barry-Jon
I posted this in the vb group as well, but just in case...
I'm not sure you're doing anything wrong, but perhaps the instructions we
use for classroom/lab installs of MSDE to work with Visual Studio .NET 2003
will be helpful:
<quote>
1. Before you begin, check the PC to ensure there are no remnants of prior
MSDE installation attempts hanging around. The place to check is: C:\Program
Files\Microsoft SQL Server. If you locate a folder named Microsoft SQL
Server, delete it and its contents!
2. Execute the file: SQL2KDeskSP3.exe(or whatever the file name for your
MSDE download is). This step will extract the contents of the file to a
designated folder. Make a note of the destination folder. You'll need it
later. This step does not install MSDE (although the dialogs seem to hint
that it does)!
4. Navigate to the folder you created in Step 2. In that folder, you will
find a subfolder named MSDE. In MSDE, you will find SETUP.EXE. Executing
SETUP.EXE will install MSDE.
5. To execute SETUP.EXE correctly, you must supply an instance name and a
system administrator password as part of the command: i.e. the command must
be:
SETUP.EXE INSTANCENAME="NetSDK" SAPWD="yourSAPassword"
where yourSAPassword is your actual system administrator password. This
password is needed only to install MDSE, not to use it. Access to MSDE is
controlled by normal "NT Security" which should allow users access based on
network logon and password. It is very important the the INSTANCENAME
parameter be NetSDK, as this name will enable you to generate the sample
databases automatically instead of having to run SQL scripts from the
command line.
6. Once installation is complete, you must reboot the PC before you will
see MSDE. After the reboot, you should see the MSDE icon in SysTray.
7. You now must execute the file: ConfigSamples.exe to configure sample
applications and MSDE system databases. This step will also create user
databases in the following location: C:\Program Files\Microsoft SQL
Server\MSSQL\Data.
</quote>
If you have trouble locating the ConfigSamples.exe, it's a small file
(56k) and I can send it to your email if needed.
Hope this helps.
Peter [MVP Visual Developer]
Jack of all trades, master of none.
|||Thanks Peter - that looks pretty much like what I did in the end. Saved
your post in case I ever forget :-)
"Peter van der Goes" <p_vandergoes@.toadstool.u> wrote in message
news:edfqWhQEFHA.3592@.TK2MSFTNGP15.phx.gbl...
> "Microsoft" <barryjonoconnell_spam_no@.yahoo.co.uk> wrote in message
> news:ucCLTwKEFHA.1188@.tk2msftngp13.phx.gbl...
> I posted this in the vb group as well, but just in case...
> I'm not sure you're doing anything wrong, but perhaps the instructions we
> use for classroom/lab installs of MSDE to work with Visual Studio .NET
> 2003 will be helpful:
> <quote>
> 1. Before you begin, check the PC to ensure there are no remnants of
> prior MSDE installation attempts hanging around. The place to check is:
> C:\Program Files\Microsoft SQL Server. If you locate a folder named
> Microsoft SQL Server, delete it and its contents!
>
> 2. Execute the file: SQL2KDeskSP3.exe(or whatever the file name for your
> MSDE download is). This step will extract the contents of the file to a
> designated folder. Make a note of the destination folder. You'll need it
> later. This step does not install MSDE (although the dialogs seem to hint
> that it does)!
>
> 4. Navigate to the folder you created in Step 2. In that folder, you will
> find a subfolder named MSDE. In MSDE, you will find SETUP.EXE. Executing
> SETUP.EXE will install MSDE.
>
> 5. To execute SETUP.EXE correctly, you must supply an instance name and a
> system administrator password as part of the command: i.e. the command
> must be:
>
> SETUP.EXE INSTANCENAME="NetSDK" SAPWD="yourSAPassword"
>
> where yourSAPassword is your actual system administrator password. This
> password is needed only to install MDSE, not to use it. Access to MSDE is
> controlled by normal "NT Security" which should allow users access based
> on network logon and password. It is very important the the INSTANCENAME
> parameter be NetSDK, as this name will enable you to generate the sample
> databases automatically instead of having to run SQL scripts from the
> command line.
>
> 6. Once installation is complete, you must reboot the PC before you will
> see MSDE. After the reboot, you should see the MSDE icon in SysTray.
>
> 7. You now must execute the file: ConfigSamples.exe to configure sample
> applications and MSDE system databases. This step will also create user
> databases in the following location: C:\Program Files\Microsoft SQL
> Server\MSSQL\Data.
> </quote>
>
> If you have trouble locating the ConfigSamples.exe, it's a small file
> (56k) and I can send it to your email if needed.
>
> Hope this helps.
>
> --
> Peter [MVP Visual Developer]
> Jack of all trades, master of none.
>

MSDE remote connection on Windows Home - Windows Authentication

I installed an MSDE on a PC running Windows Home Edition. I would like
to connect to this MSDE installation from an oher PC using Windows
Authentication.
What do I have to do (add account on Home Edition)
hi,
xavierdaull@.gmail.com wrote:
> I installed an MSDE on a PC running Windows Home Edition. I would like
> to connect to this MSDE installation from an oher PC using Windows
> Authentication.
> What do I have to do (add account on Home Edition)
without a Domain Controller, thought in a Workgroup environment, usually you
should rely on standard SQL Server authenticated connections for remote
ones, as all the authentication features are resolved and managed by the
Domain Controller it self..
you can however setup a local account to map the remote account of the other
machine... that's to say, on your local PC you have to add another account
with the very same "credentials" of other account(s) present on the remote
PCs...
all this (still) works becouse of the underlying OS gets somehow confused
and a sort of "embezzlement" where 2 differents accounts, YourPC\YourAccount
and OtherPC\YourAccount "share" a kind of uniqueness becouse of netbios
intrusion... a preventive netbios connection, even on a share or using NET
USE can help...
but this is not granted to work in future releases or even OS service
packs...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE Problem - SQL Server not found or access denied

I am running the MSDE 2000 Setup off the SQL Server 2000 Developer Edition CD.

After installation is complete, there is a service under the Control Panel -> Services window
called MSSQL$GregInstance. I then start that service.

But now when I try to connect to the database using

osql -E -S GregInstance

I get told that the SQL Server does not exist or access denied. Even though the server is running. I have also tried

osql -E -S localhost

but no luck. Why can it not find the instance of SQL Server?

Note : SQL Server 2000 is not installed on the machine, only this MSDE instance.

Thanks
GregNot to worry, I forgot to add in the name of the pc with a \ before the instance name...

i.e

osql -E -S GREG\GregInstance

MSDE periodically fails to start at startup in restricted account

I am currently running Windows XP SP2 Tablet Edition running MSDE v 8.00.761.
The problem I am having is that at random intervals MSDE fails to start. I
can only duplicate this problem while running under a restricted user
account. In the error logs the only difference I can see is that when the
service fails the “xpsqlbot.dll” starts before the database starts. I have
the restricted user account setup so that it logs in automatically using
tweak UI. Could this be a timing issue with MSDE startup? If any one could
help I would really appreciate it.
What is the error message in the system event log say?
Jim
"Avail Developer" <AvailDeveloper@.discussions.microsoft.com> wrote in
message news:72217B26-BE67-49D7-8781-F332605D6FE4@.microsoft.com...
>I am currently running Windows XP SP2 Tablet Edition running MSDE v
>8.00.761.
> The problem I am having is that at random intervals MSDE fails to start.
> I
> can only duplicate this problem while running under a restricted user
> account. In the error logs the only difference I can see is that when
> the
> service fails the "xpsqlbot.dll" starts before the database starts. I
> have
> the restricted user account setup so that it logs in automatically using
> tweak UI. Could this be a timing issue with MSDE startup? If any one
> could
> help I would really appreciate it.
>

MSDE or MS SQL Server 2000 Developer Edition ?

I have been using MSDE and I recently got Microsoft SQL ServerTM 2000 Developer Edition as part of my MAPS pack. Can and should I replace MSDE with Microsoft SQL Server 2000 Developer Edition on my development pc? Thanks in advance for any advice on pros and cons or known issues?Please excuse my ignorance -- what a MAPS pack?

I think the benefit of installing the Developer Edition would be that you'd be able to use the Client Tools -- such as Enterprise Manager and Query Analyzer. I know people that have bought just the Developer Edition for legal use of those tools.

The Developer Edition includes all of the functionality of the Enterprise Edition, but you cannot use it for production. If you are going to be developing mobile applications needing SQL Server CE, owning the Developer Edition gives you the rgiht to redistribute SQL Server CE.

This white paper explains the differences between the editions and should help you to make an informed choice:Choosing an Edition of SQL Server 2000.

Terri|||Thanks for the info. There is some (M)icrosoft (A)ction (P)ack info:

The Action Pack Update kits are sent quarterly. To see a complete listing of the
contents of the Update kit (in the US and Canada), please visit:

http://members.microsoft.com/partner/salesmarketing/partnermarket/actionpack/updatekits.aspx

Thank you for continuing your subscription to the Microsoft Action Pack!

-The Worldwide Partner Programs Team|||Everywhere it says NT and 2000. Does it run on XP. Thanks.|||Well, I can tell you that I have XP Pro an I am running SQL Server 2000 Personal Edition successfully, and my colleague is also running XP Pro but with the SQL Server 2000 Developer Edition and he has been able to use it successfully.

YMMV

Terri

MSDE multiple instances

Hello there,
I want to install multiple instances of MSDE on XP prof edition. How many
instances can i create on a single machine?
Also, any URL for this would be helpful?
Thanks,
David
hi David,
David wrote:
> Hello there,
> I want to install multiple instances of MSDE on XP prof edition. How
> many instances can i create on a single machine?
> Also, any URL for this would be helpful?
> Thanks,
> David
you can install up to 16 instances per server, but this is a theorical limit
as you will not have enought resources to serve all of them..
each additional running instance will add about 20mb of RAM requirement but
this only is the initial load, as the real load will depend on instance
activity that will end up at the Win32 process limit of addressing up to 2gb
of RAM, and many running instances will of course bring your server down to
knees...
for additional information about SQL Server memory management, please have a
look at excellent Ken Henderson's article at
http://msdn.microsoft.com/library/de...v_03252004.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE Licencing confusion

Hi,
If I install MSDE on a live deployed server and manage it using SQL Server
2000 DEVELOPER Edition, which is installed on another machine, would I be
breaking the
licencing rules?
By manage, I mean use Enterprise Manager to perform maintenance tasks etc.
Our situation is that we currently have SQL Server 7 running our business
databases. We want to upgrade to SQL Server 2000 but only have a Developer
Edition which came with our MSDN kit.
We could upgrade to v7 to v2000 but I wanted to first consider the
alternative (cheaper) options.
Ta.
Bugger, posted the question before reading this line on
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
"Note: The tools and services included with SQL Server Developer Edition may
not be used to manage production server environments."
Sorry about that. Any comments further to that or suggestions regarding what
I'm considering doing would still be most welcome.
Thanks again.
|||hi,
Swaffs wrote:
> Hi,
> If I install MSDE on a live deployed server and manage it using SQL
> Server 2000 DEVELOPER Edition, which is installed on another machine,
> would I be breaking the
> licencing rules?
> By manage, I mean use Enterprise Manager to perform maintenance tasks
> etc.
> Our situation is that we currently have SQL Server 7 running our
> business databases. We want to upgrade to SQL Server 2000 but only
> have a Developer Edition which came with our MSDN kit.
> We could upgrade to v7 to v2000 but I wanted to first consider the
> alternative (cheaper) options.
>
you would break the EULA this way.. .but you can perhaps have a look at
http://www.microsoft.com/downloads/d...displaylang=en
... it's the evaluation edition fo SQL Server 2000 with 120 days trial..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Have you tried any other tools (free tolls) to manage your database?
Linda
"Swaffs" <Swaffs@.discussions.microsoft.com> wrote in message
news:BA9533BB-5B31-430E-85CB-E709C420CF20@.microsoft.com...
> Bugger, posted the question before reading this line on
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
> "Note: The tools and services included with SQL Server Developer Edition
> may
> not be used to manage production server environments."
> Sorry about that. Any comments further to that or suggestions regarding
> what
> I'm considering doing would still be most welcome.
> Thanks again.

MSDE instance being broadcast

I work in a domain environment with a couple of Enterprise Edition SQL
Servers. Using SSMS, when I go to register a new installation and I 'Browse
for more' in the dialog box, I see a whole bunch of workstations that I know
are set up with MSDE.
How do I keep these machines from broadcasting their presence to the domain?
All these MSDE installs are strictly for local machine use only and none of
them should allow external connections. The fact that they are broadcasting
their presence (they don't have SQL Browser because they are only MSDE) I see
as a security risk. How can I stop this?
Any suggestions.
Thanks
Todd Chittenden
Yes, it is a security risk. It's been some time since I worked with MSDE,
but I would investigate disabling the ports and protocols--much as the
surface area configuration tool does for SQL Express 2005. This can be done
if the applications are coded to use the shared memory provider (and bypass
the network) and are not (in fact) shared on the net.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:E302F2D1-165D-4DDB-BCA4-9BA587CBB237@.microsoft.com...
>I work in a domain environment with a couple of Enterprise Edition SQL
> Servers. Using SSMS, when I go to register a new installation and I
> 'Browse
> for more' in the dialog box, I see a whole bunch of workstations that I
> know
> are set up with MSDE.
> How do I keep these machines from broadcasting their presence to the
> domain?
> All these MSDE installs are strictly for local machine use only and none
> of
> them should allow external connections. The fact that they are
> broadcasting
> their presence (they don't have SQL Browser because they are only MSDE) I
> see
> as a security risk. How can I stop this?
> Any suggestions.
> Thanks
> --
> Todd Chittenden
>
|||Bill:
That's all well and good, but HOW do I go about configuring an instance of
MSDE when there is no user interface installed because it came packaged as
part of some 3rd party app?
Thanks
Todd Chittenden
"William (Bill) Vaughn" wrote:

> Yes, it is a security risk. It's been some time since I worked with MSDE,
> but I would investigate disabling the ports and protocols--much as the
> surface area configuration tool does for SQL Express 2005. This can be done
> if the applications are coded to use the shared memory provider (and bypass
> the network) and are not (in fact) shared on the net.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:E302F2D1-165D-4DDB-BCA4-9BA587CBB237@.microsoft.com...
>
>
|||Again, it's been some time since I worked with MSDE and no, I know it does
not come with configuration tools. I expect you're going to have to visit
each system and run a reconfig script or use SQL Server Management studio
(not as easy). I found a site that seems to address some of these issues.
http://www.codeproject.com/database/ConfigureMSDE.asp#7. I hope it helps.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:2DF6889A-A64A-483F-BE42-766155FC8AF7@.microsoft.com...[vbcol=seagreen]
> Bill:
> That's all well and good, but HOW do I go about configuring an instance of
> MSDE when there is no user interface installed because it came packaged as
> part of some 3rd party app?
> Thanks
> --
> Todd Chittenden
> "William (Bill) Vaughn" wrote:
|||Bill:
Thanks.
Good stuff!
Todd

MSDE instance being broadcast

I work in a domain environment with a couple of Enterprise Edition SQL
Servers. Using SSMS, when I go to register a new installation and I 'Browse
for more' in the dialog box, I see a whole bunch of workstations that I know
are set up with MSDE.
How do I keep these machines from broadcasting their presence to the domain?
All these MSDE installs are strictly for local machine use only and none of
them should allow external connections. The fact that they are broadcasting
their presence (they don't have SQL Browser because they are only MSDE) I se
e
as a security risk. How can I stop this?
Any suggestions.
Thanks
--
Todd ChittendenYes, it is a security risk. It's been some time since I worked with MSDE,
but I would investigate disabling the ports and protocols--much as the
surface area configuration tool does for SQL Express 2005. This can be done
if the applications are coded to use the shared memory provider (and bypass
the network) and are not (in fact) shared on the net.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:E302F2D1-165D-4DDB-BCA4-9BA587CBB237@.microsoft.com...
>I work in a domain environment with a couple of Enterprise Edition SQL
> Servers. Using SSMS, when I go to register a new installation and I
> 'Browse
> for more' in the dialog box, I see a whole bunch of workstations that I
> know
> are set up with MSDE.
> How do I keep these machines from broadcasting their presence to the
> domain?
> All these MSDE installs are strictly for local machine use only and none
> of
> them should allow external connections. The fact that they are
> broadcasting
> their presence (they don't have SQL Browser because they are only MSDE) I
> see
> as a security risk. How can I stop this?
> Any suggestions.
> Thanks
> --
> Todd Chittenden
>|||Bill:
That's all well and good, but HOW do I go about configuring an instance of
MSDE when there is no user interface installed because it came packaged as
part of some 3rd party app?
Thanks
--
Todd Chittenden
"William (Bill) Vaughn" wrote:

> Yes, it is a security risk. It's been some time since I worked with MSDE,
> but I would investigate disabling the ports and protocols--much as the
> surface area configuration tool does for SQL Express 2005. This can be don
e
> if the applications are coded to use the shared memory provider (and bypas
s
> the network) and are not (in fact) shared on the net.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:E302F2D1-165D-4DDB-BCA4-9BA587CBB237@.microsoft.com...
>
>|||Again, it's been some time since I worked with MSDE and no, I know it does
not come with configuration tools. I expect you're going to have to visit
each system and run a reconfig script or use SQL Server Management studio
(not as easy). I found a site that seems to address some of these issues.
http://www.codeproject.com/database...gureMSDE.asp#7. I hope it helps.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:2DF6889A-A64A-483F-BE42-766155FC8AF7@.microsoft.com...[vbcol=seagreen]
> Bill:
> That's all well and good, but HOW do I go about configuring an instance of
> MSDE when there is no user interface installed because it came packaged as
> part of some 3rd party app?
> Thanks
> --
> Todd Chittenden
> "William (Bill) Vaughn" wrote:
>|||Bill:
Thanks.
Good stuff!
Todd

MSDE Installation fails

When trying to install MSDE2000 in an XP Home edition machine the
installation fails (progress bar almost gets at the end but it then rolls
back) with no message.
There is should be a log file but I do not know how to get. Also where can I
find descriptions of the error messages?
In a previous message a similar problem was solved by installing File and
Print sharing. Unfortunately I do not know what this means.
Any ideas?
Thanks
Yannis
hi Yannis,
"Yannis Makarounis" <Yannis.Makarounis@.ace-hellas.gr> ha scritto nel
messaggio news:e%23gecCVoEHA.800@.TK2MSFTNGP14.phx.gbl
> When trying to install MSDE2000 in an XP Home edition machine the
> installation fails (progress bar almost gets at the end but it then
> rolls back) with no message.
> There is should be a log file but I do not know how to get. Also
> where can I find descriptions of the error messages?
> In a previous message a similar problem was solved by installing File
> and Print sharing. Unfortunately I do not know what this means.
> Any ideas?
> Thanks
> Yannis
open the control panel applet -> services... check the "Server" service is
running... this service allows file and pront sharing activities...
if not present, select your network connection properties... File and
Printer sharing for Microsoft network must be installed if not present..
when running the MSDE setup.exe, please add the
/L*v "c:\MsdeLog.txt"
parameter, in order to log the installation process to file, about 2mb, you
can later inspect for troubleshooting, looking for
RETURN VALUE 3
entries
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE Install

I'm running Server 2003 Standard Edition... I'm having
problems installing MSDE (light).
Is it mandatory to run Server 2003 Enterprise Edition in
order to install MSDE?
Thanks!
CJ
It is not necessary to have a previous installation of any edition of SQL
Server for installing MSDE. Please go through the following Microsoft
Articles for more information and how to custom install MSDE.
Software and Hardware requirements for various editions of SQL Server 2000
http://msdn.microsoft.com/library/de...us/instsql/in_
overview_74vn.asp
http://msdn.microsoft.com/library/de...us/architec/8_
ar_ts_7eur.asp
MSDE Installation
http://msdn.microsoft.com/library/de...us/distsql/dis
tsql_3usf.asp
http://msdn.microsoft.com/library/de...us/distsql/dis
tsql_84xl.asp
Thanks
Soma Sekhara Reddy