MSDE newbie question: connection strings

I installed MSDE on a Windows XP SP1 PC on our network. We don't have a
domain controller.
If I access this database via ADO, how do I construct the connection
string? As I understand it, this is of the form:
Provider=SQLOLEDB; Data Source=server_name; Initial
Catalog=database_name; User ID=username; Password=password;
Is the server name just the name or IP address of the PC running MSDE?
Are there any other subtleties I should be aware of?
Simon Elliott http://www.ctsn.co.uk
hi Simon,
"Simon Elliott" <Simon at ctsn.co.uk> ha scritto nel messaggio
news:OuUGwZwQEHA.3580@.TK2MSFTNGP11.phx.gbl...
> I installed MSDE on a Windows XP SP1 PC on our network. We don't have a
> domain controller.
> If I access this database via ADO, how do I construct the connection
> string? As I understand it, this is of the form:
> Provider=SQLOLEDB; Data Source=server_name; Initial
> Catalog=database_name; User ID=username; Password=password;
> Is the server name just the name or IP address of the PC running MSDE?
> Are there any other subtleties I should be aware of?
if the MSDE instance has been installed as the default intance, it's name
will just be the ComputerName and/or it's IP address... if it has been
installed as a named instance, it's name will be
ComputerName\InstanceName...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE Newbie

Are there any good online resources for learning how to use MSDE?
I've been using MS-Access for years via ADO but want to try MSDE.
Thanks in advance for any suggestions
..
I suggest you
http://www.microsoft.com/sql/msde/techinfo/default.asp
"McKirahan" wrote:

> Are there any good online resources for learning how to use MSDE?
> I've been using MS-Access for years via ADO but want to try MSDE.
> Thanks in advance for any suggestions
> ..
>
>
|||Also some tips on your learning path:
1> Read about SQL Server from booksonline or some decent book
2> Just keep in mind that MSDE is a smaller version for SQL Server. Most of the related books are for sql server and hardly mention MSDE, but if you need a quick starter book on how to use MSDE, then get "Beginning Visual Basic .Net databases", it does r
efer to MSDE all the time (but is for VB.Net..)..
I would also suggest that you go thru this newsgroups' posting from past few months.. don't worry, it is not boring and too lengthy.. it's a good read. You will know what problems other people are having and how to tackle them and you will become familia
r with the MSDE world..
And then there are MS KB articles for many issues related to MSDE..
hope it helps..
dev
|||"dev_kh" <devkh@.discussions.microsoft.com> wrote in message
news:8A2E518D-07D5-4B27-990E-134E841F8036@.microsoft.com...
> Also some tips on your learning path:
> 1> Read about SQL Server from booksonline or some decent book
> 2> Just keep in mind that MSDE is a smaller version for SQL Server. Most
of the related books are for sql server and hardly mention MSDE, but if you
need a quick starter book on how to use MSDE, then get "Beginning Visual
Basic .Net databases", it does refer to MSDE all the time (but is for
VB.Net..)..
> I would also suggest that you go thru this newsgroups' posting from past
few months.. don't worry, it is not boring and too lengthy.. it's a good
read. You will know what problems other people are having and how to tackle
them and you will become familiar with the MSDE world..
> And then there are MS KB articles for many issues related to MSDE..
> hope it helps..
> dev
Thanks for the suggestions, I'll check them out. However, I was hoping for
some site suggestions along the lines of "w3schools" or "devguru"; that is,
more of an introduction to MSDE and not the full blown Microsoft approach.

MSDE Installation via Terminal Services

I'm seeing some conflicting information and wanted to try to get it
clarified. The original release of MSDE 2000 couldn't be installed from a
Terminal Services session on a TS in Application Mode. The release notes
for MSDE 2000 Release A (which contains SP3A) still mention that there could
be problems installing via Terminal Services. But KB artcle 317268 says
that you can install SP2 via Terminal Services.
So the obvious question is, can I install MSDE 2000 Release A from a W2K3
Terminal Services session while in Application Mode?
Hal Berenson, President
PredictableIT, LLC
hi Hal,
Hal Berenson wrote:
> I'm seeing some conflicting information and wanted to try to get it
> clarified. The original release of MSDE 2000 couldn't be installed
> from a Terminal Services session on a TS in Application Mode. The
> release notes for MSDE 2000 Release A (which contains SP3A) still
> mention that there could be problems installing via Terminal
> Services. But KB artcle 317268 says that you can install SP2 via
> Terminal Services.
> So the obvious question is, can I install MSDE 2000 Release A from a
> W2K3 Terminal Services session while in Application Mode?
nope, AFAIK, but never tested sp4.. I "consolidated" the original
"impossibility" :D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE Install Question

I installed MSDE using Windows authentication and gave the SA logon ID a
"strong" password. However, when I attempt to logon to the MSDE database
(via OSQL) I get a message stating something to the effect of "the logon ID
is not associated with a trusted account". I realize what this means (i.e.
the logon ID "sa" is not a Windows account). However, what I'm wondering is
how do I logon to a brand new (MSDE) server once it's been installed to use
Windows authentication if I haven't setup any accounts/roles yet?
-- Thanks, Jeff
hi Jeff,
Jeff B. wrote:
> I installed MSDE using Windows authentication and gave the SA logon
> ID a "strong" password. However, when I attempt to logon to the MSDE
> database (via OSQL) I get a message stating something to the effect
> of "the logon ID is not associated with a trusted account". I
> realize what this means (i.e. the logon ID "sa" is not a Windows
> account). However, what I'm wondering is how do I logon to a brand
> new (MSDE) server once it's been installed to use Windows
> authentication if I haven't setup any accounts/roles yet?
> -- Thanks, Jeff
by default, the Windows administrators group will be mapped to the SQL
Server BUILTIN\Administrators WinNT group, so you can log in as a Windows
admin..
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 install common sense issues?

MSDE installs via a batch file using Microsoft's setup.
Once installed does it really make sense to uninstall it?
What if Visio is already installed before my install, or some other product
that uses MSDE, what happens to that install when my install runs?
Would I need the sa password of the prior install?
If I install my database into the default instance? And then someone
uninstalls the original app (prior to my install) that installed MSDE. Does
the installation uninstall MSDE even though my app uses it too?
Is it safer always to make my database run in its own instance?
Regards...
j
hi Jeff,
"Jeff" <joedirt@.datahook.com> ha scritto nel messaggio
news:%23nD5tx8XEHA.3520@.TK2MSFTNGP10.phx.gbl...
> MSDE installs via a batch file using Microsoft's setup.
> Once installed does it really make sense to uninstall it?
I don't understand this question... if you install an application, does it
make sense uninstalling it?...
if you need that MSDE instance, don't uninstall it..

> What if Visio is already installed before my install, or some other
product
> that uses MSDE, what happens to that install when my install runs?
I don't know if Visio install a separate MSDE instance (my Visio
installation did not) .. but you can install up to 16 different instances of
MSDE.. ok that number is quite prohibitive as regard resources, as you never
will have or desire 16 running instances of MSDE on the same box..
but if you have a "particular" instance you don't want to share with other
applications, than you can install a private instance for that app and using
a "common" instance for all other databases...

> Would I need the sa password of the prior install?
as long as that instance is up, you need it...

> If I install my database into the default instance? And then someone
> uninstalls the original app (prior to my install) that installed MSDE.
Does
> the installation uninstall MSDE even though my app uses it too?
this must be asked to the ISV providing that MSDE instance... as per MSDE
original EULA it shoul'd be that way, but now MSDE is free, and each
instance can be a shared one, as long as the ISV providing it does not
specify it's reserved for his/her app(s)

> Is it safer always to make my database run in its own instance?
it really depends... personally I do not, I only have separate instances for
test under different service pack levels, but on production servers I always
ask the end user before installing if he/se needs a separate named instance
when an existing MSDE/SQL Server instance is detected..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply