Named Pipes Provider

Hi!

I tryed to make an silent mode install for SQL express edition, for example:

start/ wait setup.exe /qn ADDLOCAL=ALL SECURITYMODE=SQL SAPWD=***** SQLBROWSERAUTOSTART=1 DISABLENETWORKPROTOCOLS=0

When i run it from a .bat file it's ok but i'm using this command in a .ini file in some apllication.
It doesn't install all the SQL, i mean in services it appears only SQL Server VSS Writer.
I also get the error Named Pipes Provider. The application that i want to install gets installed but can't connect to server.
I really need some help.

Seems your server is not installed at all. If no server is running, you will see the Named Pipes Provider error. So, make your server is installed first. How do you initiate the setup from a .ini file?

Named Instances Problem (I Think)

I'm struggling a little with this. I hope someone can help.

Ho do i install SQL Server 2005 Express so i can connect to it with "localhost", not "<MACHINE_NAME>/SQLEXPRESS". I cant seem to find any obvious setting in setup.

Could anyone shed any light on this?

Regards,

Anthony

I think you want to connect only to default instance in that case just specify the instance name as default while installing sql express refer, http://msdn2.microsoft.com/en-us/library/ms143722.aspx

|||

You can use an alias configured on the clients to connect to the name only. See the BOL for more information about configuring aliases. You will have to use the SQL Server configuration manager.

Jens K. Suessmeyer

http://www.sqlserver2005.de

Named Instances

During the install SQL 2000 askes to use the default to name a instance. Is
it better to name the instance or use the default? What is the function of
instances in SQL?Hello,
With Microsoft SQL Server 2000, you have the option of installing multiple
copies, or instances of SQL Server on one computer. When setting up a new
installation of SQL Server 2000 or maintaining an existing installation,
you can specify it as:
A default instance of SQL Server.
This instance is identified by the network name of the computer on which it
is running. Applications using client software from earlier versions of SQL
Server can connect to a default instance. SQL Server version 6.5 or SQL
Server version 7.0 servers can operate as default instances. However, a
computer can have only ONE version functioning as the default instance at a
time.
A named instance of SQL Server.
This instance is identified by the network name of the computer plus an
instance name, in the format <computername>\<instancename>. Applications
must use SQL Server 2000 client components to connect to a named instance.
A computer can run any number of named instances of SQL Server
concurrently. A named instance can run at the same time as an existing
installation of SQL Server version 6.5 or SQL Server version 7.0. The
instance name cannot exceed 16 characters.
The maximum number of instances supported in SQL Server 2000 is 16. For
more information, refer to the following articles:
Multiple Instances of SQL Server
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
ar_cs_9i5u.asp
Working with Named and Multiple Instances of SQL Server 2000
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_
runsetup_2xmb.asp
Multiple Instances
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlmag2k/
html/MultipleInstances.asp
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||If the server later changes name or joins a domain will th instance name
change as well. What I'm doing is replacing are existing SQL server with a
new SQL Server. I've named the new server newsql and made it a member of a
workgroup. After I move the databses over I would then change change the
name on the old server and then make the new server the name of the old
server and join it to the domain. Will the instance name chnage when the
server's name changes?
"Sophie Guo [MSFT]" wrote:
> Hello,
> With Microsoft SQL Server 2000, you have the option of installing multiple
> copies, or instances of SQL Server on one computer. When setting up a new
> installation of SQL Server 2000 or maintaining an existing installation,
> you can specify it as:
> A default instance of SQL Server.
> This instance is identified by the network name of the computer on which it
> is running. Applications using client software from earlier versions of SQL
> Server can connect to a default instance. SQL Server version 6.5 or SQL
> Server version 7.0 servers can operate as default instances. However, a
> computer can have only ONE version functioning as the default instance at a
> time.
> A named instance of SQL Server.
> This instance is identified by the network name of the computer plus an
> instance name, in the format <computername>\<instancename>. Applications
> must use SQL Server 2000 client components to connect to a named instance.
> A computer can run any number of named instances of SQL Server
> concurrently. A named instance can run at the same time as an existing
> installation of SQL Server version 6.5 or SQL Server version 7.0. The
> instance name cannot exceed 16 characters.
> The maximum number of instances supported in SQL Server 2000 is 16. For
> more information, refer to the following articles:
> Multiple Instances of SQL Server
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
> ar_cs_9i5u.asp
> Working with Named and Multiple Instances of SQL Server 2000
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_
> runsetup_2xmb.asp
> Multiple Instances
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlmag2k/
> html/MultipleInstances.asp
>
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello,
After renaming a server, we can perform the following steps to rename SQL
server instance:
1. Restart the server and then start the SQL Server service. This should
automatically get the *new* Server name and we only need to run the
following procedures to
update syservers system table:
-- For a default instance
EXEC sp_dropserver ''old_name''
GO
EXEC sp_addserver ''new_name'', local
GO
-- For a named instance
EXEC sp_dropserver ''original_name\original_instance_name''
GO
EXEC sp_addserver ''new_server_name\instance_name'', local
GO
2. After running the sp_addserver stored procedure, we must restart the SQL
Server service for the change to take effect. The following article
describes this
scenario in more detail:
303774 BUG: "Renaming A Server" Topic in SQL Server Books Online is
Incomplete
http://support.microsoft.com/?id=303774
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Named Instances

During the install SQL 2000 askes to use the default to name a instance. I
s
it better to name the instance or use the default? What is the function of
instances in SQL?Hello,
With Microsoft SQL Server 2000, you have the option of installing multiple
copies, or instances of SQL Server on one computer. When setting up a new
installation of SQL Server 2000 or maintaining an existing installation,
you can specify it as:
A default instance of SQL Server.
This instance is identified by the network name of the computer on which it
is running. Applications using client software from earlier versions of SQL
Server can connect to a default instance. SQL Server version 6.5 or SQL
Server version 7.0 servers can operate as default instances. However, a
computer can have only ONE version functioning as the default instance at a
time.
A named instance of SQL Server.
This instance is identified by the network name of the computer plus an
instance name, in the format <computername>\<instancename>. Applications
must use SQL Server 2000 client components to connect to a named instance.
A computer can run any number of named instances of SQL Server
concurrently. A named instance can run at the same time as an existing
installation of SQL Server version 6.5 or SQL Server version 7.0. The
instance name cannot exceed 16 characters.
The maximum number of instances supported in SQL Server 2000 is 16. For
more information, refer to the following articles:
Multiple Instances of SQL Server
http://msdn.microsoft.com/library/d...-us/architec/8_
ar_cs_9i5u.asp
Working with Named and Multiple Instances of SQL Server 2000
http://msdn.microsoft.com/library/d...-us/instsql/in_
runsetup_2xmb.asp
Multiple Instances
http://msdn.microsoft.com/library/d...-us/dnsqlmag2k/
html/MultipleInstances.asp
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||If the server later changes name or joins a domain will th instance name
change as well. What I'm doing is replacing are existing SQL server with a
new SQL Server. I've named the new server newsql and made it a member of a
workgroup. After I move the databses over I would then change change the
name on the old server and then make the new server the name of the old
server and join it to the domain. Will the instance name chnage when the
server's name changes?
"Sophie Guo [MSFT]" wrote:

> Hello,
> With Microsoft SQL Server 2000, you have the option of installing multiple
> copies, or instances of SQL Server on one computer. When setting up a new
> installation of SQL Server 2000 or maintaining an existing installation,
> you can specify it as:
> A default instance of SQL Server.
> This instance is identified by the network name of the computer on which i
t
> is running. Applications using client software from earlier versions of SQ
L
> Server can connect to a default instance. SQL Server version 6.5 or SQL
> Server version 7.0 servers can operate as default instances. However, a
> computer can have only ONE version functioning as the default instance at
a
> time.
> A named instance of SQL Server.
> This instance is identified by the network name of the computer plus an
> instance name, in the format <computername>\<instancename>. Applications
> must use SQL Server 2000 client components to connect to a named instance.
> A computer can run any number of named instances of SQL Server
> concurrently. A named instance can run at the same time as an existing
> installation of SQL Server version 6.5 or SQL Server version 7.0. The
> instance name cannot exceed 16 characters.
> The maximum number of instances supported in SQL Server 2000 is 16. For
> more information, refer to the following articles:
> Multiple Instances of SQL Server
> http://msdn.microsoft.com/library/d...ft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hello,
After renaming a server, we can perform the following steps to rename SQL
server instance:
1. Restart the server and then start the SQL Server service. This should
automatically get the *new* Server name and we only need to run the
following procedures to
update syservers system table:
-- For a default instance
EXEC sp_dropserver ''old_name''
GO
EXEC sp_addserver ''new_name'', local
GO
-- For a named instance
EXEC sp_dropserver ''original_name\original_instance_name''
GO
EXEC sp_addserver ''new_server_name\instance_name'', local
GO
2. After running the sp_addserver stored procedure, we must restart the SQL
Server service for the change to take effect. The following article
describes this
scenario in more detail:
303774 BUG: "Renaming A Server" Topic in SQL Server Books Online is
Incomplete
http://support.microsoft.com/?id=303774
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

Named Instances

During the install SQL 2000 askes to use the default to name a instance. Is
it better to name the instance or use the default? What is the function of
instances in SQL?
Hello,
With Microsoft SQL Server 2000, you have the option of installing multiple
copies, or instances of SQL Server on one computer. When setting up a new
installation of SQL Server 2000 or maintaining an existing installation,
you can specify it as:
A default instance of SQL Server.
This instance is identified by the network name of the computer on which it
is running. Applications using client software from earlier versions of SQL
Server can connect to a default instance. SQL Server version 6.5 or SQL
Server version 7.0 servers can operate as default instances. However, a
computer can have only ONE version functioning as the default instance at a
time.
A named instance of SQL Server.
This instance is identified by the network name of the computer plus an
instance name, in the format <computername>\<instancename>. Applications
must use SQL Server 2000 client components to connect to a named instance.
A computer can run any number of named instances of SQL Server
concurrently. A named instance can run at the same time as an existing
installation of SQL Server version 6.5 or SQL Server version 7.0. The
instance name cannot exceed 16 characters.
The maximum number of instances supported in SQL Server 2000 is 16. For
more information, refer to the following articles:
Multiple Instances of SQL Server
http://msdn.microsoft.com/library/de...us/architec/8_
ar_cs_9i5u.asp
Working with Named and Multiple Instances of SQL Server 2000
http://msdn.microsoft.com/library/de...us/instsql/in_
runsetup_2xmb.asp
Multiple Instances
http://msdn.microsoft.com/library/de...us/dnsqlmag2k/
html/MultipleInstances.asp
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||If the server later changes name or joins a domain will th instance name
change as well. What I'm doing is replacing are existing SQL server with a
new SQL Server. I've named the new server newsql and made it a member of a
workgroup. After I move the databses over I would then change change the
name on the old server and then make the new server the name of the old
server and join it to the domain. Will the instance name chnage when the
server's name changes?
"Sophie Guo [MSFT]" wrote:

> Hello,
> With Microsoft SQL Server 2000, you have the option of installing multiple
> copies, or instances of SQL Server on one computer. When setting up a new
> installation of SQL Server 2000 or maintaining an existing installation,
> you can specify it as:
> A default instance of SQL Server.
> This instance is identified by the network name of the computer on which it
> is running. Applications using client software from earlier versions of SQL
> Server can connect to a default instance. SQL Server version 6.5 or SQL
> Server version 7.0 servers can operate as default instances. However, a
> computer can have only ONE version functioning as the default instance at a
> time.
> A named instance of SQL Server.
> This instance is identified by the network name of the computer plus an
> instance name, in the format <computername>\<instancename>. Applications
> must use SQL Server 2000 client components to connect to a named instance.
> A computer can run any number of named instances of SQL Server
> concurrently. A named instance can run at the same time as an existing
> installation of SQL Server version 6.5 or SQL Server version 7.0. The
> instance name cannot exceed 16 characters.
> The maximum number of instances supported in SQL Server 2000 is 16. For
> more information, refer to the following articles:
> Multiple Instances of SQL Server
> http://msdn.microsoft.com/library/de...us/architec/8_
> ar_cs_9i5u.asp
> Working with Named and Multiple Instances of SQL Server 2000
> http://msdn.microsoft.com/library/de...us/instsql/in_
> runsetup_2xmb.asp
> Multiple Instances
> http://msdn.microsoft.com/library/de...us/dnsqlmag2k/
> html/MultipleInstances.asp
>
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hello,
After renaming a server, we can perform the following steps to rename SQL
server instance:
1. Restart the server and then start the SQL Server service. This should
automatically get the *new* Server name and we only need to run the
following procedures to
update syservers system table:
-- For a default instance
EXEC sp_dropserver ''old_name''
GO
EXEC sp_addserver ''new_name'', local
GO
-- For a named instance
EXEC sp_dropserver ''original_name\original_instance_name''
GO
EXEC sp_addserver ''new_server_name\instance_name'', local
GO
2. After running the sp_addserver stored procedure, we must restart the SQL
Server service for the change to take effect. The following article
describes this
scenario in more detail:
303774 BUG: "Renaming A Server" Topic in SQL Server Books Online is
Incomplete
http://support.microsoft.com/?id=303774
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Named instance, no default instance -> connection problems?

Hey,
I have the following problem with deployment of MSDE. Here's what I want
to do:
- I want to install MSDE in a named instance, even if it wasn't installed
before.
- I want to connect to the local server only, if possible with a
"generic" name, so I don't have to look up the system name
and stuff.
I can't really get this to work at all. I have connection strings that
work fine on development machines (where the default instance name is
used), using . for the server name. On the test machine, using
..\MYINSTANCE doesn't work at all. I read suggestions to use
(local)\MYINSTANCE instead of .\MYINSTANCE, but to no avail.
The funny thing is, even SYSTEMNAME\MYINSTANCE doesn't work unless there's
a default instance running on the same machine. Plus, it seems cumbersome
to have to find out the system's name for such a purpose.
Maybe I'm just seriously wrong about something... I didn't think it would
be that hard to set up a local (!, no networking enabled) database server
using the standard (!, they do say I'm to use a vendor-specific instance,
don't they?) setup procedure and connect to that.
Any ideas, please?
Oliver Sturm
omnibus ex nihilo ducendis sufficit unum
MSN oliver@.sturmnet.org Jabber sturm@.amessage.de ICQ 27142619
hi Oliver,
"Oliver Sturm" <oliver@.sturmnet.org> ha scritto nel messaggio
news:pan.2004.06.18.10.39.55.285051@.sturmnet.org.. .
> Hey,
> I have the following problem with deployment of MSDE. Here's what I want
> to do:
> - I want to install MSDE in a named instance, even if it wasn't installed
> before.
> - I want to connect to the local server only, if possible with a
> "generic" name, so I don't have to look up the system name
> and stuff.
> I can't really get this to work at all. I have connection strings that
> work fine on development machines (where the default instance name is
> used), using . for the server name. On the test machine, using
> .\MYINSTANCE doesn't work at all. I read suggestions to use
> (local)\MYINSTANCE instead of .\MYINSTANCE, but to no avail.
> The funny thing is, even SYSTEMNAME\MYINSTANCE doesn't work unless there's
> a default instance running on the same machine. Plus, it seems cumbersome
> to have to find out the system's name for such a purpose.
> Maybe I'm just seriously wrong about something... I didn't think it would
> be that hard to set up a local (!, no networking enabled) database server
> using the standard (!, they do say I'm to use a vendor-specific instance,
> don't they?) setup procedure and connect to that.
> Any ideas, please?
that's weird, becouse (local)\InstanceName shoul'd be fine..... ok, I'm
running a pc with a default instance and a named instance...
as regard the ComputerName part, remember you are trying to connect to a
service specified on the target pc...
you can always set an Alias via Client Network Utility, but this is not the
case... but building the connection string using something similar to Public
Declare Function GetComputerName Lib "kernel32" Alias "GetComputerNameA"
(ByVal lpBuffer As String, nSize As Long) As Long, appending the
"\YourInstanceName", in your preferred language, coul'd solve the problem
too...
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
sql

named instance and default instance: same port

When one install a named instance in addition to a default instance on the
same server, does the named instance also get assigned to the same port 1433
? ThanksNamed instances dynamically assign an unused TCP port number the first time
the instance is started. You can use the server network utility to see the
port number you've got. BTW, there is a listener service which runs on UDP
port 1434 but doesn't have a service name on the
machine. This listener service exposes which SQL Server instances are
installed, and their associated port numbers.
HTH,
Paul Ibisonsql

named instance and default instance: same port

When one install a named instance in addition to a default instance on the
same server, does the named instance also get assigned to the same port 1433
? ThanksNamed instances dynamically assign an unused TCP port number the first time
the instance is started. You can use the server network utility to see the
port number you've got. BTW, there is a listener service which runs on UDP
port 1434 but doesn't have a service name on the
machine. This listener service exposes which SQL Server instances are
installed, and their associated port numbers.
HTH,
Paul Ibison

named instance and default instance: same port

When one install a named instance in addition to a default instance on the
same server, does the named instance also get assigned to the same port 1433
? Thanks
Named instances dynamically assign an unused TCP port number the first time
the instance is started. You can use the server network utility to see the
port number you've got. BTW, there is a listener service which runs on UDP
port 1434 but doesn't have a service name on the
machine. This listener service exposes which SQL Server instances are
installed, and their associated port numbers.
HTH,
Paul Ibison

named instance after install?

can I change my SQL2k desktop server to a named instance after install?
--== Posted via mcse.ms - Unlimited-Uncensored-Secure Usenet News==-
--
http://www.mcse.ms The #1 Newsgroup Service in the World! 120,000+ New
sgroups
--= East and West-Coast Server Farms - Total Privacy via Encryption =--I believe that will require a new installation.
This is my signature. It is a general reminder.
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.
"David J Rose" <david.rose@.newsgroup.reply.only.com> wrote in message
news:426662c7$1_2@.127.0.0.1...
> can I change my SQL2k desktop server to a named instance after install?|||Each instance is it's own installation, with own binaries and files. You nee
d
to do a full un-install and re-install.
Regards
Mike
"David J Rose" wrote:

> can I change my SQL2k desktop server to a named instance after install?
>
> --== Posted via mcse.ms - Unlimited-Uncensored-Secure Usenet News=
=--
> http://www.mcse.ms The #1 Newsgroup Service in the World! 120,000+ N
ewsgroups
> --= East and West-Coast Server Farms - Total Privacy via Encryption =--
-
>

Named Instance

hi,
i wanted to have my 2 node server cluster as active-active. DO i need to put
the named pipes in both servers before i install sql2000 or just on the one
that i wanted to install the instance?i will have VSS1/INST1 and VSS2/INST2.
do i need to put both of them in CNU and install sql on first node and
proceed to another? pls advice.. just a bit blur on that part.Also when do i
need to remove this named pipes? JUST after installation and sqlspa3
completed?
TIA
Hi
During the SQL Server Install on a cluster, the setup creates the instances
and copies the binaries to all nodes. It is not a good idea to have any SQL
server installed intances prior to configuring clustering.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"rupart" wrote:

> hi,
> i wanted to have my 2 node server cluster as active-active. DO i need to put
> the named pipes in both servers before i install sql2000 or just on the one
> that i wanted to install the instance?i will have VSS1/INST1 and VSS2/INST2.
> do i need to put both of them in CNU and install sql on first node and
> proceed to another? pls advice.. just a bit blur on that part.Also when do i
> need to remove this named pipes? JUST after installation and sqlspa3
> completed?
> TIA

n00b Question Re: MSDE SQL Server Install

I am trying to install some code on my website which is called EasyDisk. It
creates a forum, like any forum you see anywhere. Anyways it requires an SQL
Server, so I acquired MSDE SQL Server 2000. I created an instance of it, and
can see the folder on my C drive. The instance is called
MYFIRSTDBMSSQL$MYFIRSTDB oddly enough since I guess I didn't understand the
instruction for naming an instance. In any case, the forum software requires
I know 1. The name of my SQL Server, 2. My username 3. My password and 4. My
database name.
So, best I can tell my db name is my instance name, and my username and
password are what I use to log onto Windows XP. How far off am I? ... and I
have no idea what my sql server name is. How do I find out? The Books online
is no help whatsoever in this regard.
Thanks,
Jim
hi Jim,
"newgenre" <newgenre@.mindspring.com> ha scritto nel messaggio
news:%xchc.3922$e4.2441@.newsread2.news.pas.earthli nk.net...
>.....
> I know 1. The name of my SQL Server, 2. My username 3. My password and 4.
My
> database name.
> So, best I can tell my db name is my instance name, and my username and
> password are what I use to log onto Windows XP. How far off am I? ... and
I
> have no idea what my sql server name is. How do I find out? The Books
online
> is no help whatsoever in this regard.
your instance name shoul'd be MYFIRSTDB (and you can verify this opening
your service management applet, in the part right to the $ sign)... the
service manager in your tray bar area shoul'd provide this information
too...
so the full instance name is YourComputerName\MYFIRSTDB
your db name for the connection string is not the instance name, but the
database you want to connect to..
as regard your credential, it depends on the authentication mode you want to
connect to SQL Server with..
SQL Server accepst 2 kinds of authentication mode:
trusted (WinNT) authentication, where you are not required to provide user's
information;
SQL Server authentication, where you have to provide them in the form of
"user id=username;password=yourStrongPwd;" as indicated in
http://www.connectionstrings.com/ ...
you can find more about authentication modes beginning at
http://msdn.microsoft.com/library/de...setup_6p9v.asp
you can find which kind of authentication your MSDE instance supports by
inspecting the registry at the
HKLM\Software\Microsoft\Microsoft SQL
Server\YourInstanceName\MSSQLServer\LoginMode key
a value of 0 or 2 specifies Mixed mode (both modes), while a value of 1
spefies truste authentication only.
hth
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
sql

n00b Question Re: MSDE SQL Server Install

Sorry if I sound to simple for you, I'm not sure what your
experience is, and this is how I understand it best.)
SQL Server runs as a Service. That's an app that runs in
the background.
You can have more that one 'Instance' of SQL Server
running at a time. (The number allowed depends on the
version you install.) This allows, let's say, your Website
database running in one instance to crash without having
your accounting db (on another instance) going down also.
On each instance of SQL Server, you can have a number of
Databases.
Hopes that clears some things up. Did you install MSDE (MS
SQL Server Desktop Edition) or SQL Server
Standard/Enterprise/Personal edition?
MSDE does not install some management tools that make
things real easy.
It was Desktop Edition.
"M K" <mark@.nospamcenturycolor.com> wrote in message
news:252001c427c3$54b21740$a001280a@.phx.gbl...
> Sorry if I sound to simple for you, I'm not sure what your
> experience is, and this is how I understand it best.)
> SQL Server runs as a Service. That's an app that runs in
> the background.
> You can have more that one 'Instance' of SQL Server
> running at a time. (The number allowed depends on the
> version you install.) This allows, let's say, your Website
> database running in one instance to crash without having
> your accounting db (on another instance) going down also.
> On each instance of SQL Server, you can have a number of
> Databases.
> Hopes that clears some things up. Did you install MSDE (MS
> SQL Server Desktop Edition) or SQL Server
> Standard/Enterprise/Personal edition?
> MSDE does not install some management tools that make
> things real easy.
|||Yea, Desktop Edition, MSDE, is the redistribution version.
Stripped down. I would think your app would create the
database for itself.
If you don't have a version of SQL running you can install
MSDE with mostly defaults. You don't need to set an
Instance. Then install the app and it should set up the
database.
I hate it when I don't have enough documentation, don't
you.

MySQL OLEDB Driver

Hi!

I have a small question, there are OLEDB drivers availible for .NET on the MYSQL download site. But when I install them I'm not able to see them inside SQLIS, I've tried them inside Visual Studio and they work fine.

Is there a way to get them "registred" or add them as a reference inside SQLIS so that I may choose them when setting up an OLEDB Source / Destination?For performance reasons, the Integration Services Service caches (as DTS used to do) the list of available components and, among other things, OLE DB Providers, so that the designer doesn't need to waste time gathering those lists from the registry and the file system. I'm just speculating here, but I'm guessing that you might need to do something to refresh that cached list, such as stop and re-start the Service (or reboot). A little-known dialog box in DTS times has a "Refresh Cache" button, but I haven't seen an equivalent button in SSIS.

-Doug
|||Don't think that's the problem, I think the problem is that the driver doesn't get registered in the windows registery. Is there a way to add some keys to the windows registery to manually register the .dll files as OLEDB drivers?|||Hi, have you figured out that one?|||You say OLEDB drivers for .NET but that doesn't make sense to me. OLEDB is not a .NET provider instead it would be ADO.NET. Are the drivers OLEDB or are they .NET. If they are .NET then they wouldn't be available from our OLEDB source but from our DataReaderSource, which uses .NET connections. If they are indeed OLEDB then if they are not showing up then they are not registering themselves correctly. You could try regsvr32 to reregister them but you might have to contact MySQL support and ask them for help.

Thanks,
Matt

MySQL OLEDB Driver

Hi!

I have a small question, there are OLEDB drivers availible for .NET on the MYSQL download site. But when I install them I'm not able to see them inside SQLIS, I've tried them inside Visual Studio and they work fine.

Is there a way to get them "registred" or add them as a reference inside SQLIS so that I may choose them when setting up an OLEDB Source / Destination?For performance reasons, the Integration Services Service caches (as DTS used to do) the list of available components and, among other things, OLE DB Providers, so that the designer doesn't need to waste time gathering those lists from the registry and the file system. I'm just speculating here, but I'm guessing that you might need to do something to refresh that cached list, such as stop and re-start the Service (or reboot). A little-known dialog box in DTS times has a "Refresh Cache" button, but I haven't seen an equivalent button in SSIS.

-Doug
|||Don't think that's the problem, I think the problem is that the driver doesn't get registered in the windows registery. Is there a way to add some keys to the windows registery to manually register the .dll files as OLEDB drivers?|||Hi, have you figured out that one?|||You say OLEDB drivers for .NET but that doesn't make sense to me. OLEDB is not a .NET provider instead it would be ADO.NET. Are the drivers OLEDB or are they .NET. If they are .NET then they wouldn't be available from our OLEDB source but from our DataReaderSource, which uses .NET connections. If they are indeed OLEDB then if they are not showing up then they are not registering themselves correctly. You could try regsvr32 to reregister them but you might have to contact MySQL support and ask them for help.

Thanks,
Matt

mysql installation problem in Xp

hello !

I am not able to install Mysql on my pc runnig XP
..the log file shows server is readyfor connection on port 3306.

but still client not able to server .
error comes can't connect localhaost to server on port 10061

winmysqladmin showing green indiacting server is running but server
and lient info are not there.

pls help.

smita[posted and mailed]

Smita (smitap56@.rediffmail.com) writes:
> I am not able to install Mysql on my pc runnig XP
> .the log file shows server is readyfor connection on port 3306.
> but still client not able to server .
> error comes can't connect localhaost to server on port 10061
> winmysqladmin showing green indiacting server is running but server
> and lient info are not there.

Please try http://www.mysql.com. I believe they have some support forum
there. In this group we discsuss Microsoft SQL Server, so we can't help
you.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

MySql 64 bit driver and SSIS

If anyone have been able to install the MySql ODBC driver on XP 64 bit and get it to work with SSIS, PLEASE tell me how you accomplished it.

Duplicate post (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2055272&SiteID=1)

Some related posts that might help :

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=165801&SiteID=1

MySql 64 bit driver and SSIS

If anyone have been able to install the MySql ODBC driver on XP 64 bit and get it to work with SSIS, PLEASE tell me how you accomplished it.

Duplicate post (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2055272&SiteID=1)

Some related posts that might help :

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=165801&SiteID=1

mysql

hey I'm just trying to install mysql and it keeps saying
I need a strong password for SA. I thought I did and I'm
sure this is really simple. Thanks!This is a newsgroup for Microsoft SQL server. If you have a question about
that product, someone here will be glad to help you.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Tony" <anonymous@.discussions.microsoft.com> wrote in message
news:577501c40072$e9c72230$a501280a@.phx.gbl...
> hey I'm just trying to install mysql and it keeps saying
> I need a strong password for SA. I thought I did and I'm
> sure this is really simple. Thanks!|||Strong pwds consist of a mixture of upper and lower case letters, are genera
lly more than 8 characters long and contain at least one number.

my sqlsp.log

this is the end of my sqlsp.log after sp3a install to existing SQL 200
11:03:54 Begin: SetupRegistry(
11:03:54 Register this installation of SQL Server with MDA
11:03:54 Completed registering this installation of SQL Server with MDA
11:03:55 Start Process...updating reg entries for S
11:03:55 No Server -> Tool
11:03:55 End: SetupRegistry(
11:03:55 Begin: PostSetupRegistry(
11:03:55 C:\PROGRA~1\COMMON~1\MICROS~1\SQLDEB~1\SQLDBR~1.EXE sqldbreg2.exe -RegServe
11:03:56 End: PostSetupRegistry(
11:04:07 You should now backup your master and msdb databases since this installation has updated their content
11:04:07 Action CleanUpInstall
11:04:09 Installation Completed with Errors (number of nonfatal errors: 1
But when I check @.@.version I am still on sp2. Did not see indication of what the nonfatal error was. Idea what I should be looking for?The last line says: 11:04:09 Installation Completed with
Errors (number of nonfatal errors: 1)
Your SQL SP# installation was not succesfull, please fix
the issue and re-install em
Thank you,
Saleem Hakani
>--Original Message--
>this is the end of my sqlsp.log after sp3a install to
existing SQL 2000
>11:03:54 Begin: SetupRegistry()
>11:03:54 Register this installation of SQL Server with
MDAC
>11:03:54 Completed registering this installation of SQL
Server with MDAC
>11:03:55 Start Process...updating reg entries for SP
>11:03:55 No Server -> Tools
>11:03:55 End: SetupRegistry()
>11:03:55 Begin: PostSetupRegistry()
>11:03:55 C:\PROGRA~1\COMMON~1\MICROS~1\SQLDEB~1
\SQLDBR~1.EXE sqldbreg2.exe -RegServer
>11:03:56 End: PostSetupRegistry()
>11:04:07 You should now backup your master and msdb
databases since this installation has updated their
content.
>11:04:07 Action CleanUpInstall:
>11:04:09 Installation Completed with Errors (number of
nonfatal errors: 1)
>But when I check @.@.version I am still on sp2. Did not
see indication of what the nonfatal error was. Idea what
I should be looking for?
>.
>