Showing posts with label installed. Show all posts
Showing posts with label installed. Show all posts

Friday, March 30, 2012

How to control SQL Server 2005 Express installed as a "prerequisite"


Suppose I check "SQL Server 2005 Express Edition" as one of the prerequisites for a custom app in a Windows Setup project.

From reading whatever docs I could get my hands on, it's still not clear to me how to control the installation of SQL Server Express with respect to things like instance name, service account, etc, etc.

In other words, this is stuff that's normally the domain of template.ini. However, there's no clear indication of where I should put template.ini so that the install of "prerequisite" SQL Server Express will see it and configure accordingly...

Thanks in advance to anyone who can help solve this...

Josh

Josh, template.ini is not used for configuration settings (as the .iss files were in SQL 2000). This file merely is used as documentation for creating silent installs by describing which flags are used in various situations.

As for another application installing SQL 2005 Express, I would assume that the application is controlling the install (instance name, accounts, etc) so that it can connect after install. If they are not exposing these install features during their install, they probably are using some default values for all installs.

Thanks,
Samuel Lester (MSFT)

|||

Samuel:

Yep, it looks like the parameters (at least, all the ones I tried) are recognized when supplied on the command line.

One parameter I haven't been able to find, though, is one that tells SQL Server Express Edition to use port 1433 instead of dynamic ports. I know about DISABLENETWORKPROTOCOLS (and it, too, works as expected), but it only activates TCP -- it doesn't affect the port-assignment scheme.

Thanks,
Josh

Wednesday, March 28, 2012

How to connect to the SQl server EXPRESS using 'ODBC Data Source A

Hi All,
Recently I have installed SQl server express edition. I was able to connect
to the SQL server from my .NET project using connection parameter like:
Data Source=.\SQLEXPRESS;AttachDbFilename=C:\Documents and Settings\Raju\My
Documents\Sanjib SQL DBs\IBuyAdventure\IBuyAdventure.mdf;Integrated
Security=True;Connect Timeout=30;User Instance=True
Now I need to connect to the same SQL server from 'ODBC Data Source
Aministrator' wizard, that I am unable to do. The wizard is asking me (for
system DSn and File DSN) for SQL server name (I do no know what to give, is
it (local) or something) and how to login authenticate (with windows
authentication or something). Now if I goto Services/SQl Server (SQLEXPRESS)
, click LogOn I see that 'Local System Account' is checked. Pls tell me how
to connect to this SQl server using System DSN connection wizard.
By the way I am the administrator of this machine where I have instlled the
SQl server...
Thanks in advance,
--
Sanjib SahaHi
VB.NET
Imports System.Data.Odbc
Dim oODBCConnection As OdbcConnection
Dim ConnString As String = _
"Driver={SQL Server};" & _
"Server=SQLServerName;" & _
"Database=DatabaseName;" & _
"Uid=Username;" & _
"Pwd=Password"
oODBCConnection = New Odbc.OdbcConnection(ConnString)
oODBCConnection.Open()
"sanjib" <sanjib@.discussions.microsoft.com> wrote in message
news:7BE14AB4-9460-4489-B7CB-62880592EFC6@.microsoft.com...
> Hi All,
> Recently I have installed SQl server express edition. I was able to
> connect
> to the SQL server from my .NET project using connection parameter like:
> Data Source=.\SQLEXPRESS;AttachDbFilename=C:\Documents and
> Settings\Raju\My
> Documents\Sanjib SQL DBs\IBuyAdventure\IBuyAdventure.mdf;Integrated
> Security=True;Connect Timeout=30;User Instance=True
> Now I need to connect to the same SQL server from 'ODBC Data Source
> Aministrator' wizard, that I am unable to do. The wizard is asking me (for
> system DSn and File DSN) for SQL server name (I do no know what to give,
> is
> it (local) or something) and how to login authenticate (with windows
> authentication or something). Now if I goto Services/SQl Server
> (SQLEXPRESS)
> , click LogOn I see that 'Local System Account' is checked. Pls tell me
> how
> to connect to this SQl server using System DSN connection wizard.
> By the way I am the administrator of this machine where I have instlled
> the
> SQl server...
> Thanks in advance,
> --
> Sanjib Saha|||The OP indicates that he is using SQL Server 2005 Express' User Instance. I
do not think he can connect to User Instance through ODBC DSN Wizard (why
use ODBC anyway?). I am not should if it is possible to connect to SQL
Server Express' User Instance through OdbcConnection object in
System.Data.Odbc namespace, but it is certain your sample code will not.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23QvKqzLoGHA.4332@.TK2MSFTNGP03.phx.gbl...
> Hi
> VB.NET
> Imports System.Data.Odbc
> Dim oODBCConnection As OdbcConnection
> Dim ConnString As String = _
> "Driver={SQL Server};" & _
> "Server=SQLServerName;" & _
> "Database=DatabaseName;" & _
> "Uid=Username;" & _
> "Pwd=Password"
> oODBCConnection = New Odbc.OdbcConnection(ConnString)
> oODBCConnection.Open()
>
> "sanjib" <sanjib@.discussions.microsoft.com> wrote in message
> news:7BE14AB4-9460-4489-B7CB-62880592EFC6@.microsoft.com...
>> Hi All,
>> Recently I have installed SQl server express edition. I was able to
>> connect
>> to the SQL server from my .NET project using connection parameter like:
>> Data Source=.\SQLEXPRESS;AttachDbFilename=C:\Documents and
>> Settings\Raju\My
>> Documents\Sanjib SQL DBs\IBuyAdventure\IBuyAdventure.mdf;Integrated
>> Security=True;Connect Timeout=30;User Instance=True
>> Now I need to connect to the same SQL server from 'ODBC Data Source
>> Aministrator' wizard, that I am unable to do. The wizard is asking me
>> (for
>> system DSn and File DSN) for SQL server name (I do no know what to give,
>> is
>> it (local) or something) and how to login authenticate (with windows
>> authentication or something). Now if I goto Services/SQl Server
>> (SQLEXPRESS)
>> , click LogOn I see that 'Local System Account' is checked. Pls tell me
>> how
>> to connect to this SQl server using System DSN connection wizard.
>> By the way I am the administrator of this machine where I have instlled
>> the
>> SQl server...
>> Thanks in advance,
>> --
>> Sanjib Saha
>|||Norman,
There should be some way to connect to the SQl server 2005 Express user
instance. I need to connect to this SQl server b'case one of my application
is demandint that...There should be some way, tht we do not know...Anyway
thanks...Someone pls guide me...
Thanks,
Sanjib
--
Sanjib Saha
"sanjib" wrote:
> Hi All,
> Recently I have installed SQl server express edition. I was able to connect
> to the SQL server from my .NET project using connection parameter like:
> Data Source=.\SQLEXPRESS;AttachDbFilename=C:\Documents and Settings\Raju\My
> Documents\Sanjib SQL DBs\IBuyAdventure\IBuyAdventure.mdf;Integrated
> Security=True;Connect Timeout=30;User Instance=True
> Now I need to connect to the same SQL server from 'ODBC Data Source
> Aministrator' wizard, that I am unable to do. The wizard is asking me (for
> system DSn and File DSN) for SQL server name (I do no know what to give, is
> it (local) or something) and how to login authenticate (with windows
> authentication or something). Now if I goto Services/SQl Server (SQLEXPRESS)
> , click LogOn I see that 'Local System Account' is checked. Pls tell me how
> to connect to this SQl server using System DSN connection wizard.
> By the way I am the administrator of this machine where I have instlled the
> SQl server...
> Thanks in advance,
> --
> Sanjib Saha|||You can access an User Instance once it is started by specifying the Named
Pipe name for the instance but if you haven't already started the user
instance with a managed code connection, ODBC won't start it. If your main
application is using ODBC, I would recommend attaching the database to the
main instance so it is always running and the ODBC connection can find it.
There is more information on named instances and how to connect to them
here:
http://msdn.microsoft.com/sql/express/default.aspx?pull=/library/en-us/dnsse/html/sqlexpuserinst.asp
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"sanjib" <sanjib@.discussions.microsoft.com> wrote in message
news:2AB671B3-FEAD-49C9-A309-8DBF8BF07815@.microsoft.com...
> Norman,
> There should be some way to connect to the SQl server 2005 Express user
> instance. I need to connect to this SQl server b'case one of my
> application
> is demandint that...There should be some way, tht we do not know...Anyway
> thanks...Someone pls guide me...
> Thanks,
> Sanjib
> --
> Sanjib Saha
>
> "sanjib" wrote:
>> Hi All,
>> Recently I have installed SQl server express edition. I was able to
>> connect
>> to the SQL server from my .NET project using connection parameter like:
>> Data Source=.\SQLEXPRESS;AttachDbFilename=C:\Documents and
>> Settings\Raju\My
>> Documents\Sanjib SQL DBs\IBuyAdventure\IBuyAdventure.mdf;Integrated
>> Security=True;Connect Timeout=30;User Instance=True
>> Now I need to connect to the same SQL server from 'ODBC Data Source
>> Aministrator' wizard, that I am unable to do. The wizard is asking me
>> (for
>> system DSn and File DSN) for SQL server name (I do no know what to give,
>> is
>> it (local) or something) and how to login authenticate (with windows
>> authentication or something). Now if I goto Services/SQl Server
>> (SQLEXPRESS)
>> , click LogOn I see that 'Local System Account' is checked. Pls tell me
>> how
>> to connect to this SQl server using System DSN connection wizard.
>> By the way I am the administrator of this machine where I have instlled
>> the
>> SQl server...
>> Thanks in advance,
>> --
>> Sanjib Saha|||I agree with Roger.
If you HAVE to access the database on SQL Server Express via something other
than ADO.NET2.0's System.Data SqlClient namespace, why use User Instannce?
The whole point of using user instance is to limit the database setup/access
within current user's privilidge of access to the computer. If a user has to
use ODBC DSN Wizard, it may well requires the user has a bit more privilidge
that usual. Also, an user instance is not available to other user even the
other user uses the same computer.
"sanjib" <sanjib@.discussions.microsoft.com> wrote in message
news:2AB671B3-FEAD-49C9-A309-8DBF8BF07815@.microsoft.com...
> Norman,
> There should be some way to connect to the SQl server 2005 Express user
> instance. I need to connect to this SQl server b'case one of my
> application
> is demandint that...There should be some way, tht we do not know...Anyway
> thanks...Someone pls guide me...
> Thanks,
> Sanjib
> --
> Sanjib Saha
>
> "sanjib" wrote:
>> Hi All,
>> Recently I have installed SQl server express edition. I was able to
>> connect
>> to the SQL server from my .NET project using connection parameter like:
>> Data Source=.\SQLEXPRESS;AttachDbFilename=C:\Documents and
>> Settings\Raju\My
>> Documents\Sanjib SQL DBs\IBuyAdventure\IBuyAdventure.mdf;Integrated
>> Security=True;Connect Timeout=30;User Instance=True
>> Now I need to connect to the same SQL server from 'ODBC Data Source
>> Aministrator' wizard, that I am unable to do. The wizard is asking me
>> (for
>> system DSn and File DSN) for SQL server name (I do no know what to give,
>> is
>> it (local) or something) and how to login authenticate (with windows
>> authentication or something). Now if I goto Services/SQl Server
>> (SQLEXPRESS)
>> , click LogOn I see that 'Local System Account' is checked. Pls tell me
>> how
>> to connect to this SQl server using System DSN connection wizard.
>> By the way I am the administrator of this machine where I have instlled
>> the
>> SQl server...
>> Thanks in advance,
>> --
>> Sanjib Saha|||Roger/Norman,
The whole point came like this. I am trying to install a SQl server driven
3rd party application and after the applications gets installed the database
installation wizard appears and tht wizard asks me to connect to the SQL
server using ODBC DSN, so I need to know the parameters for connecting to the
SQL server, which I don't know it seems, b'case while installing SQL server
2005 it never asked me for a server name/login password. And now it is
running using the 'Local System Account' i.e. Local Admin account that is me.
May be my SQL server 2005 is using user instance, although I am not sure.
The fact that I am not that much knowlegeble in SQL severs, much worked in
microsoft programming languages, and SQl server for me is a database server
tht always worked.
I will try from the URL provided by Roger and let u know...
Thanks,
Sanjib
--
Sanjib Saha
"Roger Wolter[MSFT]" wrote:
> You can access an User Instance once it is started by specifying the Named
> Pipe name for the instance but if you haven't already started the user
> instance with a managed code connection, ODBC won't start it. If your main
> application is using ODBC, I would recommend attaching the database to the
> main instance so it is always running and the ODBC connection can find it.
> There is more information on named instances and how to connect to them
> here:
> http://msdn.microsoft.com/sql/express/default.aspx?pull=/library/en-us/dnsse/html/sqlexpuserinst.asp
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "sanjib" <sanjib@.discussions.microsoft.com> wrote in message
> news:2AB671B3-FEAD-49C9-A309-8DBF8BF07815@.microsoft.com...
> > Norman,
> >
> > There should be some way to connect to the SQl server 2005 Express user
> > instance. I need to connect to this SQl server b'case one of my
> > application
> > is demandint that...There should be some way, tht we do not know...Anyway
> > thanks...Someone pls guide me...
> >
> > Thanks,
> > Sanjib
> > --
> > Sanjib Saha
> >
> >
> > "sanjib" wrote:
> >
> >> Hi All,
> >>
> >> Recently I have installed SQl server express edition. I was able to
> >> connect
> >> to the SQL server from my .NET project using connection parameter like:
> >>
> >> Data Source=.\SQLEXPRESS;AttachDbFilename=C:\Documents and
> >> Settings\Raju\My
> >> Documents\Sanjib SQL DBs\IBuyAdventure\IBuyAdventure.mdf;Integrated
> >> Security=True;Connect Timeout=30;User Instance=True
> >>
> >> Now I need to connect to the same SQL server from 'ODBC Data Source
> >> Aministrator' wizard, that I am unable to do. The wizard is asking me
> >> (for
> >> system DSn and File DSN) for SQL server name (I do no know what to give,
> >> is
> >> it (local) or something) and how to login authenticate (with windows
> >> authentication or something). Now if I goto Services/SQl Server
> >> (SQLEXPRESS)
> >> , click LogOn I see that 'Local System Account' is checked. Pls tell me
> >> how
> >> to connect to this SQl server using System DSN connection wizard.
> >>
> >> By the way I am the administrator of this machine where I have instlled
> >> the
> >> SQl server...
> >>
> >> Thanks in advance,
> >> --
> >> Sanjib Saha
>
>|||From your description in this post, it seems your installation does not
install an user instance (I am not sure). However, form your first post,
according to the ConnectionString, you are trying to use an User Instance.
User Instance of SQL Server Express is a special installation of SQL Server
Express. It seems you need a bit more study on what an user instance is, so
that you can tell if your intallation is an user instance or not, and
whether you need an user instance or not. IMO, SQL Server Express's user
instance does not go with ODBC.
"sanjib" <sanjib@.discussions.microsoft.com> wrote in message
news:33A10BC3-2103-4BD3-B9E7-5AE71965D745@.microsoft.com...
> Roger/Norman,
> The whole point came like this. I am trying to install a SQl server driven
> 3rd party application and after the applications gets installed the
> database
> installation wizard appears and tht wizard asks me to connect to the SQL
> server using ODBC DSN, so I need to know the parameters for connecting to
> the
> SQL server, which I don't know it seems, b'case while installing SQL
> server
> 2005 it never asked me for a server name/login password. And now it is
> running using the 'Local System Account' i.e. Local Admin account that is
> me.
> May be my SQL server 2005 is using user instance, although I am not sure.
> The fact that I am not that much knowlegeble in SQL severs, much worked in
> microsoft programming languages, and SQl server for me is a database
> server
> tht always worked.
> I will try from the URL provided by Roger and let u know...
> Thanks,
> Sanjib
> --
> Sanjib Saha
>
> "Roger Wolter[MSFT]" wrote:
>> You can access an User Instance once it is started by specifying the
>> Named
>> Pipe name for the instance but if you haven't already started the user
>> instance with a managed code connection, ODBC won't start it. If your
>> main
>> application is using ODBC, I would recommend attaching the database to
>> the
>> main instance so it is always running and the ODBC connection can find
>> it.
>> There is more information on named instances and how to connect to them
>> here:
>> http://msdn.microsoft.com/sql/express/default.aspx?pull=/library/en-us/dnsse/html/sqlexpuserinst.asp
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "sanjib" <sanjib@.discussions.microsoft.com> wrote in message
>> news:2AB671B3-FEAD-49C9-A309-8DBF8BF07815@.microsoft.com...
>> > Norman,
>> >
>> > There should be some way to connect to the SQl server 2005 Express user
>> > instance. I need to connect to this SQl server b'case one of my
>> > application
>> > is demandint that...There should be some way, tht we do not
>> > know...Anyway
>> > thanks...Someone pls guide me...
>> >
>> > Thanks,
>> > Sanjib
>> > --
>> > Sanjib Saha
>> >
>> >
>> > "sanjib" wrote:
>> >
>> >> Hi All,
>> >>
>> >> Recently I have installed SQl server express edition. I was able to
>> >> connect
>> >> to the SQL server from my .NET project using connection parameter
>> >> like:
>> >>
>> >> Data Source=.\SQLEXPRESS;AttachDbFilename=C:\Documents and
>> >> Settings\Raju\My
>> >> Documents\Sanjib SQL DBs\IBuyAdventure\IBuyAdventure.mdf;Integrated
>> >> Security=True;Connect Timeout=30;User Instance=True
>> >>
>> >> Now I need to connect to the same SQL server from 'ODBC Data Source
>> >> Aministrator' wizard, that I am unable to do. The wizard is asking me
>> >> (for
>> >> system DSn and File DSN) for SQL server name (I do no know what to
>> >> give,
>> >> is
>> >> it (local) or something) and how to login authenticate (with windows
>> >> authentication or something). Now if I goto Services/SQl Server
>> >> (SQLEXPRESS)
>> >> , click LogOn I see that 'Local System Account' is checked. Pls tell
>> >> me
>> >> how
>> >> to connect to this SQl server using System DSN connection wizard.
>> >>
>> >> By the way I am the administrator of this machine where I have
>> >> instlled
>> >> the
>> >> SQl server...
>> >>
>> >> Thanks in advance,
>> >> --
>> >> Sanjib Saha
>>|||I think I may understand what you're asking now. You have two completely
unrelated elements in your posting. First you were able to use ADO.Net in
Visual Studio to create a database. This database was a user instance which
is why this came up in our answers. On a completely unrelated note you now
want to install a third party application that uses ODBC to connect to the
database.
Go into the Windows Control Panel and select Administrative Tools. One of
the tools is ODBC data sources. Select the System DSN or User DSN as
required for your application and click ADD. Select the SQL Native Client
Driver. Fill in a name which you get to choose (probably the application is
looking for a particular name), leave the description blank and put
.\SQLExpress in the server field. Select the defaults for the rest unless
you already know the database name you want to make your default database.
If not, the default will be "master".
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Norman Yuan" <NotReal@.NotReal.not> wrote in message
news:eQyQnkToGHA.956@.TK2MSFTNGP03.phx.gbl...
>I agree with Roger.
> If you HAVE to access the database on SQL Server Express via something
> other than ADO.NET2.0's System.Data SqlClient namespace, why use User
> Instannce? The whole point of using user instance is to limit the database
> setup/access within current user's privilidge of access to the computer.
> If a user has to use ODBC DSN Wizard, it may well requires the user has a
> bit more privilidge that usual. Also, an user instance is not available to
> other user even the other user uses the same computer.
>
> "sanjib" <sanjib@.discussions.microsoft.com> wrote in message
> news:2AB671B3-FEAD-49C9-A309-8DBF8BF07815@.microsoft.com...
>> Norman,
>> There should be some way to connect to the SQl server 2005 Express user
>> instance. I need to connect to this SQl server b'case one of my
>> application
>> is demandint that...There should be some way, tht we do not
>> know...Anyway
>> thanks...Someone pls guide me...
>> Thanks,
>> Sanjib
>> --
>> Sanjib Saha
>>
>> "sanjib" wrote:
>> Hi All,
>> Recently I have installed SQl server express edition. I was able to
>> connect
>> to the SQL server from my .NET project using connection parameter like:
>> Data Source=.\SQLEXPRESS;AttachDbFilename=C:\Documents and
>> Settings\Raju\My
>> Documents\Sanjib SQL DBs\IBuyAdventure\IBuyAdventure.mdf;Integrated
>> Security=True;Connect Timeout=30;User Instance=True
>> Now I need to connect to the same SQL server from 'ODBC Data Source
>> Aministrator' wizard, that I am unable to do. The wizard is asking me
>> (for
>> system DSn and File DSN) for SQL server name (I do no know what to give,
>> is
>> it (local) or something) and how to login authenticate (with windows
>> authentication or something). Now if I goto Services/SQl Server
>> (SQLEXPRESS)
>> , click LogOn I see that 'Local System Account' is checked. Pls tell me
>> how
>> to connect to this SQl server using System DSN connection wizard.
>> By the way I am the administrator of this machine where I have instlled
>> the
>> SQl server...
>> Thanks in advance,
>> --
>> Sanjib Saha
>|||Roger/Norman,
Roger's trick to connect to the SQL server worked for me, I was able to use
the ODBC data source wizard to connect to the SQL server. It worked for me.
Now I will be happy if this SQL server let me create a user (for this SQL
server) for me, at least one user with all the DBA permission. Is tht
possible, pls let me know...
By the time I have started reading some materials for SQL server. ANother
thing with this SQL server 2005 express, there is no SQl explore window where
I can find create the SQL server Datavase/queries etc. Why is it so.
Although many thanks for your kind help and suggestions...
Sanjib
--
Sanjib Saha
"Roger Wolter[MSFT]" wrote:
> I think I may understand what you're asking now. You have two completely
> unrelated elements in your posting. First you were able to use ADO.Net in
> Visual Studio to create a database. This database was a user instance which
> is why this came up in our answers. On a completely unrelated note you now
> want to install a third party application that uses ODBC to connect to the
> database.
> Go into the Windows Control Panel and select Administrative Tools. One of
> the tools is ODBC data sources. Select the System DSN or User DSN as
> required for your application and click ADD. Select the SQL Native Client
> Driver. Fill in a name which you get to choose (probably the application is
> looking for a particular name), leave the description blank and put
> ..\SQLExpress in the server field. Select the defaults for the rest unless
> you already know the database name you want to make your default database.
> If not, the default will be "master".
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Norman Yuan" <NotReal@.NotReal.not> wrote in message
> news:eQyQnkToGHA.956@.TK2MSFTNGP03.phx.gbl...
> >I agree with Roger.
> >
> > If you HAVE to access the database on SQL Server Express via something
> > other than ADO.NET2.0's System.Data SqlClient namespace, why use User
> > Instannce? The whole point of using user instance is to limit the database
> > setup/access within current user's privilidge of access to the computer.
> > If a user has to use ODBC DSN Wizard, it may well requires the user has a
> > bit more privilidge that usual. Also, an user instance is not available to
> > other user even the other user uses the same computer.
> >
> >
> > "sanjib" <sanjib@.discussions.microsoft.com> wrote in message
> > news:2AB671B3-FEAD-49C9-A309-8DBF8BF07815@.microsoft.com...
> >> Norman,
> >>
> >> There should be some way to connect to the SQl server 2005 Express user
> >> instance. I need to connect to this SQl server b'case one of my
> >> application
> >> is demandint that...There should be some way, tht we do not
> >> know...Anyway
> >> thanks...Someone pls guide me...
> >>
> >> Thanks,
> >> Sanjib
> >> --
> >> Sanjib Saha
> >>
> >>
> >> "sanjib" wrote:
> >>
> >> Hi All,
> >>
> >> Recently I have installed SQl server express edition. I was able to
> >> connect
> >> to the SQL server from my .NET project using connection parameter like:
> >>
> >> Data Source=.\SQLEXPRESS;AttachDbFilename=C:\Documents and
> >> Settings\Raju\My
> >> Documents\Sanjib SQL DBs\IBuyAdventure\IBuyAdventure.mdf;Integrated
> >> Security=True;Connect Timeout=30;User Instance=True
> >>
> >> Now I need to connect to the same SQL server from 'ODBC Data Source
> >> Aministrator' wizard, that I am unable to do. The wizard is asking me
> >> (for
> >> system DSn and File DSN) for SQL server name (I do no know what to give,
> >> is
> >> it (local) or something) and how to login authenticate (with windows
> >> authentication or something). Now if I goto Services/SQl Server
> >> (SQLEXPRESS)
> >> , click LogOn I see that 'Local System Account' is checked. Pls tell me
> >> how
> >> to connect to this SQl server using System DSN connection wizard.
> >>
> >> By the way I am the administrator of this machine where I have instlled
> >> the
> >> SQl server...
> >>
> >> Thanks in advance,
> >> --
> >> Sanjib Saha
> >
> >
>
>|||You can download Sql Server Management Studio Express (free) from MS and it
is desinged for managing SQL Server /Express,
"sanjib" <sanjib@.discussions.microsoft.com> wrote in message
news:7AC96FD6-B69E-4A90-8CB7-C5151A5BD193@.microsoft.com...
> Roger/Norman,
> Roger's trick to connect to the SQL server worked for me, I was able to
> use
> the ODBC data source wizard to connect to the SQL server. It worked for
> me.
> Now I will be happy if this SQL server let me create a user (for this SQL
> server) for me, at least one user with all the DBA permission. Is tht
> possible, pls let me know...
> By the time I have started reading some materials for SQL server. ANother
> thing with this SQL server 2005 express, there is no SQl explore window
> where
> I can find create the SQL server Datavase/queries etc. Why is it so.
> Although many thanks for your kind help and suggestions...
> Sanjib
> --
> Sanjib Saha
>
> "Roger Wolter[MSFT]" wrote:
>> I think I may understand what you're asking now. You have two completely
>> unrelated elements in your posting. First you were able to use ADO.Net
>> in
>> Visual Studio to create a database. This database was a user instance
>> which
>> is why this came up in our answers. On a completely unrelated note you
>> now
>> want to install a third party application that uses ODBC to connect to
>> the
>> database.
>> Go into the Windows Control Panel and select Administrative Tools. One
>> of
>> the tools is ODBC data sources. Select the System DSN or User DSN as
>> required for your application and click ADD. Select the SQL Native
>> Client
>> Driver. Fill in a name which you get to choose (probably the application
>> is
>> looking for a particular name), leave the description blank and put
>> ..\SQLExpress in the server field. Select the defaults for the rest
>> unless
>> you already know the database name you want to make your default
>> database.
>> If not, the default will be "master".
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Norman Yuan" <NotReal@.NotReal.not> wrote in message
>> news:eQyQnkToGHA.956@.TK2MSFTNGP03.phx.gbl...
>> >I agree with Roger.
>> >
>> > If you HAVE to access the database on SQL Server Express via something
>> > other than ADO.NET2.0's System.Data SqlClient namespace, why use User
>> > Instannce? The whole point of using user instance is to limit the
>> > database
>> > setup/access within current user's privilidge of access to the
>> > computer.
>> > If a user has to use ODBC DSN Wizard, it may well requires the user has
>> > a
>> > bit more privilidge that usual. Also, an user instance is not available
>> > to
>> > other user even the other user uses the same computer.
>> >
>> >
>> > "sanjib" <sanjib@.discussions.microsoft.com> wrote in message
>> > news:2AB671B3-FEAD-49C9-A309-8DBF8BF07815@.microsoft.com...
>> >> Norman,
>> >>
>> >> There should be some way to connect to the SQl server 2005 Express
>> >> user
>> >> instance. I need to connect to this SQl server b'case one of my
>> >> application
>> >> is demandint that...There should be some way, tht we do not
>> >> know...Anyway
>> >> thanks...Someone pls guide me...
>> >>
>> >> Thanks,
>> >> Sanjib
>> >> --
>> >> Sanjib Saha
>> >>
>> >>
>> >> "sanjib" wrote:
>> >>
>> >> Hi All,
>> >>
>> >> Recently I have installed SQl server express edition. I was able to
>> >> connect
>> >> to the SQL server from my .NET project using connection parameter
>> >> like:
>> >>
>> >> Data Source=.\SQLEXPRESS;AttachDbFilename=C:\Documents and
>> >> Settings\Raju\My
>> >> Documents\Sanjib SQL DBs\IBuyAdventure\IBuyAdventure.mdf;Integrated
>> >> Security=True;Connect Timeout=30;User Instance=True
>> >>
>> >> Now I need to connect to the same SQL server from 'ODBC Data Source
>> >> Aministrator' wizard, that I am unable to do. The wizard is asking me
>> >> (for
>> >> system DSn and File DSN) for SQL server name (I do no know what to
>> >> give,
>> >> is
>> >> it (local) or something) and how to login authenticate (with windows
>> >> authentication or something). Now if I goto Services/SQl Server
>> >> (SQLEXPRESS)
>> >> , click LogOn I see that 'Local System Account' is checked. Pls tell
>> >> me
>> >> how
>> >> to connect to this SQl server using System DSN connection wizard.
>> >>
>> >> By the way I am the administrator of this machine where I have
>> >> instlled
>> >> the
>> >> SQl server...
>> >>
>> >> Thanks in advance,
>> >> --
>> >> Sanjib Saha
>> >
>> >
>>

How to connect to the SQl server EXPRESS using 'ODBC Data Source A

Hi All,
Recently I have installed SQl server express edition. I was able to connect
to the SQL server from my .NET project using connection parameter like:
Data Source=. \SQLEXPRESS;AttachDbFilename=C:\Document
s and Settings\Raju\My
Documents\Sanjib SQL DBs\IBuyAdventure\IBuyAdventure.mdf;Integrated
Security=True;Connect Timeout=30;User Instance=True
Now I need to connect to the same SQL server from 'ODBC Data Source
Aministrator' wizard, that I am unable to do. The wizard is asking me (for
system DSn and File DSN) for SQL server name (I do no know what to give, is
it (local) or something) and how to login authenticate (with windows
authentication or something). Now if I goto Services/SQl Server (SQLEXPRESS)
, click LogOn I see that 'Local System Account' is checked. Pls tell me how
to connect to this SQl server using System DSN connection wizard.
By the way I am the administrator of this machine where I have instlled the
SQl server...
Thanks in advance,
--
Sanjib SahaHi
VB.NET
Imports System.Data.Odbc
Dim oODBCConnection As OdbcConnection
Dim ConnString As String = _
"Driver={SQL Server};" & _
"Server=SQLServerName;" & _
"Database=DatabaseName;" & _
"Uid=Username;" & _
"Pwd=Password"
oODBCConnection = New Odbc.OdbcConnection(ConnString)
oODBCConnection.Open()
"sanjib" <sanjib@.discussions.microsoft.com> wrote in message
news:7BE14AB4-9460-4489-B7CB-62880592EFC6@.microsoft.com...
> Hi All,
> Recently I have installed SQl server express edition. I was able to
> connect
> to the SQL server from my .NET project using connection parameter like:
> Data Source=. \SQLEXPRESS;AttachDbFilename=C:\Document
s and
> Settings\Raju\My
> Documents\Sanjib SQL DBs\IBuyAdventure\IBuyAdventure.mdf;Integrated
> Security=True;Connect Timeout=30;User Instance=True
> Now I need to connect to the same SQL server from 'ODBC Data Source
> Aministrator' wizard, that I am unable to do. The wizard is asking me (for
> system DSn and File DSN) for SQL server name (I do no know what to give,
> is
> it (local) or something) and how to login authenticate (with windows
> authentication or something). Now if I goto Services/SQl Server
> (SQLEXPRESS)
> , click LogOn I see that 'Local System Account' is checked. Pls tell me
> how
> to connect to this SQl server using System DSN connection wizard.
> By the way I am the administrator of this machine where I have instlled
> the
> SQl server...
> Thanks in advance,
> --
> Sanjib Saha|||The OP indicates that he is using SQL Server 2005 Express' User Instance. I
do not think he can connect to User Instance through ODBC DSN Wizard (why
use ODBC anyway?). I am not should if it is possible to connect to SQL
Server Express' User Instance through OdbcConnection object in
System.Data.Odbc namespace, but it is certain your sample code will not.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23QvKqzLoGHA.4332@.TK2MSFTNGP03.phx.gbl...
> Hi
> VB.NET
> Imports System.Data.Odbc
> Dim oODBCConnection As OdbcConnection
> Dim ConnString As String = _
> "Driver={SQL Server};" & _
> "Server=SQLServerName;" & _
> "Database=DatabaseName;" & _
> "Uid=Username;" & _
> "Pwd=Password"
> oODBCConnection = New Odbc.OdbcConnection(ConnString)
> oODBCConnection.Open()
>
> "sanjib" <sanjib@.discussions.microsoft.com> wrote in message
> news:7BE14AB4-9460-4489-B7CB-62880592EFC6@.microsoft.com...
>|||Norman,
There should be some way to connect to the SQl server 2005 Express user
instance. I need to connect to this SQl server b'case one of my application
is demandint that...There should be some way, tht we do not know...Anyway
thanks...Someone pls guide me...
Thanks,
Sanjib
--
Sanjib Saha
"sanjib" wrote:

> Hi All,
> Recently I have installed SQl server express edition. I was able to connec
t
> to the SQL server from my .NET project using connection parameter like:
> Data Source=. \SQLEXPRESS;AttachDbFilename=C:\Document
s and Settings\Raju\M
y
> Documents\Sanjib SQL DBs\IBuyAdventure\IBuyAdventure.mdf;Integrated
> Security=True;Connect Timeout=30;User Instance=True
> Now I need to connect to the same SQL server from 'ODBC Data Source
> Aministrator' wizard, that I am unable to do. The wizard is asking me (for
> system DSn and File DSN) for SQL server name (I do no know what to give, i
s
> it (local) or something) and how to login authenticate (with windows
> authentication or something). Now if I goto Services/SQl Server (SQLEXPRES
S)
> , click LogOn I see that 'Local System Account' is checked. Pls tell me ho
w
> to connect to this SQl server using System DSN connection wizard.
> By the way I am the administrator of this machine where I have instlled th
e
> SQl server...
> Thanks in advance,
> --
> Sanjib Saha|||You can access an User Instance once it is started by specifying the Named
Pipe name for the instance but if you haven't already started the user
instance with a managed code connection, ODBC won't start it. If your main
application is using ODBC, I would recommend attaching the database to the
main instance so it is always running and the ODBC connection can find it.
There is more information on named instances and how to connect to them
here:
http://msdn.microsoft.com/sql/expre...expuserinst.asp
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"sanjib" <sanjib@.discussions.microsoft.com> wrote in message
news:2AB671B3-FEAD-49C9-A309-8DBF8BF07815@.microsoft.com...[vbcol=seagreen]
> Norman,
> There should be some way to connect to the SQl server 2005 Express user
> instance. I need to connect to this SQl server b'case one of my
> application
> is demandint that...There should be some way, tht we do not know...Anyway
> thanks...Someone pls guide me...
> Thanks,
> Sanjib
> --
> Sanjib Saha
>
> "sanjib" wrote:
>|||I agree with Roger.
If you HAVE to access the database on SQL Server Express via something other
than ADO.NET2.0's System.Data SqlClient namespace, why use User Instannce?
The whole point of using user instance is to limit the database setup/access
within current user's privilidge of access to the computer. If a user has to
use ODBC DSN Wizard, it may well requires the user has a bit more privilidge
that usual. Also, an user instance is not available to other user even the
other user uses the same computer.
"sanjib" <sanjib@.discussions.microsoft.com> wrote in message
news:2AB671B3-FEAD-49C9-A309-8DBF8BF07815@.microsoft.com...[vbcol=seagreen]
> Norman,
> There should be some way to connect to the SQl server 2005 Express user
> instance. I need to connect to this SQl server b'case one of my
> application
> is demandint that...There should be some way, tht we do not know...Anyway
> thanks...Someone pls guide me...
> Thanks,
> Sanjib
> --
> Sanjib Saha
>
> "sanjib" wrote:
>|||I think I may understand what you're asking now. You have two completely
unrelated elements in your posting. First you were able to use ADO.Net in
Visual Studio to create a database. This database was a user instance which
is why this came up in our answers. On a completely unrelated note you now
want to install a third party application that uses ODBC to connect to the
database.
Go into the Windows Control Panel and select Administrative Tools. One of
the tools is ODBC data sources. Select the System DSN or User DSN as
required for your application and click ADD. Select the SQL Native Client
Driver. Fill in a name which you get to choose (probably the application is
looking for a particular name), leave the description blank and put
.\SQLExpress in the server field. Select the defaults for the rest unless
you already know the database name you want to make your default database.
If not, the default will be "master".
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Norman Yuan" <NotReal@.NotReal.not> wrote in message
news:eQyQnkToGHA.956@.TK2MSFTNGP03.phx.gbl...
>I agree with Roger.
> If you HAVE to access the database on SQL Server Express via something
> other than ADO.NET2.0's System.Data SqlClient namespace, why use User
> Instannce? The whole point of using user instance is to limit the database
> setup/access within current user's privilidge of access to the computer.
> If a user has to use ODBC DSN Wizard, it may well requires the user has a
> bit more privilidge that usual. Also, an user instance is not available to
> other user even the other user uses the same computer.
>
> "sanjib" <sanjib@.discussions.microsoft.com> wrote in message
> news:2AB671B3-FEAD-49C9-A309-8DBF8BF07815@.microsoft.com...
>

How to connect to the June Katmai CTP?

Hi all,

I'm new to the Katmai SQL Server. I have just installed the June CTP x64 developer edition on a Win2003 Server AMD x64 bit. I installed everything. The install went fine.

My question:

How do I connect to the Katmai? There where no Management Studio in the install package.

The SQL Server 2005 Management Studio will not connect. It says that it can only connect to SQL 2000 or SQL 2005.

Best regards,

Lars-Inge

(Lars-Inge Tønnessen@.discussions.microsoft.com) writes: > I'm new to the Katmai SQL Server. I have just installed the June CTP x64 > developer edition on a Win2003 Server AMD x64 bit. I installed > everything. The install went fine. > > > > My question: > > How do I connect to the Katmai? There where no Management Studio in the > install package. There was in mine. Hm, I installed 32-bit. Could it be that tools are in the 32-bit distribution? (Tools are 32-bit anyway.) Also, look for a setup in the Tools directory if there is one. > The SQL Server 2005 Management Studio will not connect. It says that it > can only connect to SQL 2000 or SQL 2005. SQLCMD and OSQL works. And Query Analyzer from SQL 2000, if you have it around. -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||I also tried to install SQL 2008 on VPC for Orcas. I see only configuration tools.

how to connect to SQL server express 2005 database at the same time from both SSMSE and VB2005 a

Here is the situation:

I have SQL server express 2005 installed on my pc as instance SQLEXPRESS.

I have created a Visual Basic applicaion with the following as connection to the SQL server express 2005 running on the same PC:
****************************************************************************************************
Dim lconnectionString As String
Dim builder As New SqlConnectionStringBuilder
Dim cmd As New SqlCommand
Dim reader As SqlDataReader
Dim parameter As SqlParameter


builder("Data Source") = ".\SQLEXPRESS"
builder("Initial Catalog") = ""
builder("AttachDbFilename") = "C:\My Documents\Visual Studio 2005\Projects\abc\abc\abc.mdf"
builder("Integrated Security") = True
builder("User Instance") = True
lconnectionString = builder.ConnectionString

Dim sqlConnection1 As New SqlConnection(lconnectionString)

cmd.CommandText = "SP_add_collection"
cmd.CommandType = CommandType.StoredProcedure
cmd.Connection = sqlConnection1

sqlConnection1.Open()
*******************************************************************************************************************

It seems that i can not connect to the abc.mdf in SSMSE while the VB program is running. (ERROR:
Database 'C:\My Documents\Visual Studio 2005\Projects\abc\abc\abc.mdf' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. (.Net SqlClient Data Provider) )

If i connect to the abc.mdf first in SSMSE, then run the VB program afterwards, it gives me the error on this line -- sqlConnection1.Open()

I want to be able to access the abc.mdf database with both SSMSE and VB at the same time. Could anyone help me on this ?

Thanks very much !

apple

I'll go out on a limb here and assume that you've attached the .mdf to SSMSE which is essentially just a pointer to the db. It is not technically a SQL database.

When you're connecting the .mdf through code, use the same connection as if you were connecting to MS Access.

If you have a stored procedure that uses the .mdf, use a sql connection.

Good luck,

Adamus

|||yes, i attached the .mdf file to the SSMSE. and i call the stored procedures in the VB application.

I want to see the result of data change of the VB application in the SSMSE right away, while the application updates the date in the table. is it possible ?|||

Yes it's possible but you have to connect directly to the .mdf not SSMS.

Adamus

sql

how to connect to SQL server express 2005 database at the same time from both SSMSE and VB20

Here is the situation:

I have SQL server express 2005 installed on my pc as instance SQLEXPRESS.

I have created a Visual Basic applicaion with the following as connection to the SQL server express 2005 running on the same PC:
****************************************************************************************************
Dim lconnectionString As String
Dim builder As New SqlConnectionStringBuilder
Dim cmd As New SqlCommand
Dim reader As SqlDataReader
Dim parameter As SqlParameter


builder("Data Source") = ".\SQLEXPRESS"
builder("Initial Catalog") = ""
builder("AttachDbFilename") = "C:\My Documents\Visual Studio 2005\Projects\abc\abc\abc.mdf"
builder("Integrated Security") = True
builder("User Instance") = True
lconnectionString = builder.ConnectionString

Dim sqlConnection1 As New SqlConnection(lconnectionString)

cmd.CommandText = "SP_add_collection"
cmd.CommandType = CommandType.StoredProcedure
cmd.Connection = sqlConnection1

sqlConnection1.Open()
*******************************************************************************************************************

It seems that i can not connect to the abc.mdf in SSMSE while the VB program is running. (ERROR:
Database 'C:\My Documents\Visual Studio 2005\Projects\abc\abc\abc.mdf' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. (.Net SqlClient Data Provider) )

If i connect to the abc.mdf first in SSMSE, then run the VB program afterwards, it gives me the error on this line -- sqlConnection1.Open()

I want to be able to access the abc.mdf database with both SSMSE and VB at the same time. Could anyone help me on this ?

Thanks very much !

apple

I'll go out on a limb here and assume that you've attached the .mdf to SSMSE which is essentially just a pointer to the db. It is not technically a SQL database.

When you're connecting the .mdf through code, use the same connection as if you were connecting to MS Access.

If you have a stored procedure that uses the .mdf, use a sql connection.

Good luck,

Adamus

|||yes, i attached the .mdf file to the SSMSE. and i call the stored procedures in the VB application.

I want to see the result of data change of the VB application in the SSMSE right away, while the application updates the date in the table. is it possible ?|||

Yes it's possible but you have to connect directly to the .mdf not SSMS.

Adamus

How to connect to SQL server 2005 from C# after default installation?

Hi everyone,

I just installed Visual Studio 2005 and SQL Server 2005. However, I`m not able to connect to the database.

When running this C# code, I get a SqlException.

using System; using System.Data; using System.Data.SqlClient; class Program {
static void Main(string[] args) {
SqlConnection connection = new SqlConnection(); connection.ConnectionString = "Data Source=(local)\\sqlexpress;Initial Catalog=X;Integrated Security=True;"; connection.Open(); connection.Close();
}
}

I get the following error message:

Cannot open database X requested by the login. The login failed.
Login failed for user Y.

Can anyone tell me how to connect to sql server 2005 after default installation? Any help would be appreciated! :-)

Jan

Most likely your user ID does not exist in a list of the logins for the database. You need to grant an access for your Windows account to the database. Check next links with some info

http://support.microsoft.com/kb/325003/en-us#XSLTH4213121122120121120120

http://support.microsoft.com/kb/240872/en-us

|||Thx, my program runs!

I executed the following command (in VS Command Prompt) to add my windows account to the list of database accounts.

C:\>osql -E -S (local)\sqlexpress
1> EXEC sp_grantlogin 'machine_name\user_name'
2> go
1> exit

How to Connect to SQL Server 2005 enterprise version

I've just installed sql server 2005 enterprise on my Windows XP Professional
SP2 machine.
I can't find a way to connect with it.
I'm totaly new to SQL Server and have installed it to learn about it.
I can' t even find out if it is running or not.
When I do a
c:>netstat -a
I can't find the port number 1433 in the list.
I've checked the services but can't find the name there
Thanks in advance,
WillyThis may help. It's a new tutorial I wrote for the coming web release of
Books Online.
Getting Started with the Database Engine
Welcome to the Getting Started with the Database Engine tutorial. This
tutorial is intended for users who are new to SQL Server 2005 and who have
installed Developer, Express, or Evaluation Edition on a computer running
Windows XP Professional Service Pack 1 (SP1).This brief tutorial helps you
get started using the Database Engine.
What You Will Learn
This tutorial shows you how to connect to the Database Engine using SQL
Server Management Studio or Management Studio Express, on both the local
computer and from another computer.
This tutorial is divided into two lessons:
Lesson 1: Connecting to the Database Engine
In this lesson, you will learn how to connect to the Database Engine and
enable additional people to connect.
Lesson 2: Connecting from Another Computer
In this lesson, you will learn how to connect to the Database Engine from a
second computer, including enabling protocols, configuring ports, and
configuring firewall settings.
Requirements
This lesson has no knowledge prerequisites.
Your system must have the following installed to use this tutorial:
a.. Internet Explorer 6.0 or later.
b.. Either SQL Server Management Studio or Management Studio Express.
Lesson 1: Connecting to the Database Engine
When you install the SQL Server 2005 Database Engine, the tools that are
installed depend upon the edition and your setup choices. This lesson
reviews the principal tools, and shows you how to connect and perform a
basic function (authorizing more users).
This lesson contains the following topics:
a.. Tools for Getting Started
b.. Connecting with Management Studio
c.. Authorizing Additional Connections
Tools for Getting Started
The SQL Server 2005 Database Engine ships with a variety of tools. This
topic describes the first tools you will need, and helps you select the
right tool for the job. All tools can be accessed from the Start menu.
Generally, tools such as SQL Server Management Studio are not installed by
default. You must select the tools as part of the client components during
setup. For complete description of the tools described below, search for
them in Books Online. SQL Server 2005 Express Edition contains only a subset
of the tools.
Basic Tools
a.. SQL Server Management Studio is the principal tool for administering
the Database Engine and writing Transact-SQL code. It is hosted in the
Visual Studio shell. It is not included in SQL Server 2005 Express Edition
or SQL Server 2005 Mobile Edition.
b.. SQL Server Management Studio Express is a free, limited version of SQL
Server Management Studio, intended for use with SQL Server 2005 Express
Edition and for users who want the basic features of Management Studio in a
lightweight tool.
c.. SQL Server Surface Area Configuration installs with SQL Server and
lets you enable the server protocols, configure services to start
automatically, and enable some optional features of the Database Engine.
d.. SQL Server Configuration Manager installs with both SQL Server and the
client tools. It lets you enable server protocols, configure protocol
options such as TCP ports, configure server services to start automatically,
and configure client computers to connect in your preferred manner.
Sample Database
SQL Server 2005 includes a sample database called AdventureWorks. This
database is not installed by default. If you wish to experiment with the
AdventureWorks database, you must select it using the Setup program. Most
examples described in Books Online use the AdventureWorks database. For more
information, see Running Setup to Install AdventureWorks Sample Databases
and Samples.
To start SQL Server Management Studio
1. On the Start menu, point to All Programs, point to Microsoft SQL
Server 2005, and then click SQL Server Management Studio.
To start SQL Server Surface Area Configuration or SQL Server Configuration
Manager
1. On the Start menu, point to All Programs, point to Microsoft SQL
Server 2005, point to Configuration Tools, and then click either SQL Server
Surface Area Configuration or SQL Server Configuration Manager.
Connecting with Management Studio
It is easy to connect to the Database Engine from tools running on the same
computer if you know the name of the instance, and if you are connecting as
a member of the Administrators group on the computer. The following
procedures must be performed on the same computer that hosts SQL Server.
To determine the name of the Database Engine instance
1. Log into Windows as a member of the Administrators group, and open
either Management Studio or Management Studio Express Edition.
The Connect to Server dialog box opens.
2. Click Cancel.
3. If Registered Servers is not displayed, on the View menu, click
Registered Servers.
4. With Database Engine selected on the Registered Servers toolbar,
right-click Database Engine, and then click Update Local Server
Registration. All instances of the Database Engine installed on the computer
are displayed. This includes instances of SQL Server 2000. Management Studio
can connect and manage instances of SQL Server 2000 as well as SQL Server
2005. The default instance is unnamed and is shown as the computer name. A
named instance displays as the computer name followed by a backward slash
(\) and then the name of the instance. For SQL Server 2005 Express Edition,
the instance is named <computer_name>\sqlexpress unless the name was changed
during setup.
To verify that the Database Engine is running
1. In Registered Servers, if the name of your instance of SQL Server
has a green dot with a white arrow next to the name, the Database Engine is
running and no further action is necessary.
2. If the name of your instance of SQL Server has a red dot with a
white square next to the name, the Database Engine is stopped. Right-click
the name of the Database Engine, and then click Start. After a confirmation
dialog box, the Database Engine should start and the circle should turn
green.
To connect to the Database Engine
1. On the File menu, click Connect Object Explorer.
The Connect to Server dialog box opens. The Server type box displays the
type that was last used.
2. Select Database Engine.
3. In the Server name box, type the name of the Database Engine
instance.
4. Click Connect.
Authorizing Additional Connections
Now that you have connected to SQL Server as an administrator, one of your
first tasks is to authorize other users to connect. You do this by creating
a login and authorizing that login to access a database as a user. Logins
can be either Windows Authentication logins, which use your Windows
credentials, or SQL Server Authentication logins, which store the
authentication information in SQL Server and are independent of your network
credentials. Use Windows Authentication whenever possible.
Create a Windows Authentication login
1. In the previous task, you connected to the Database Engine using
Management Studio. In Object Explorer, expand your server instance, expand
Security, right-click Logins, and then click New Login.
The Login - New dialog box appears.
2. On the General page, in the Login name box, type a Windows login in
the format <domain>\<login>.
3. In the Default database box, select AdventureWorks if available.
Otherwise select master.
4. On the Server Roles page, if the new login is to be an
administrator, click sysadmin, otherwise leave this blank.
5. On the User Mapping page, select Map for the AdventureWorks
database if it is available. Otherwise select master. Note that the User box
is populated with the login. When closed, the dialog box will create this
user in the database.
6. In the Default Schema box, type dbo to map the login to the
database administrator schema.
7. Accept the default settings for the Securables and Status boxes and
click OK to create the login.
Note:
This is basic information to get you started. SQL Server provides a
rich security environment, and security is obviously an important aspect of
database operations. For more information about security, read the security
sections of Books Online, starting with Security Considerations for
Databases and Database Applications.
Lesson 2: Connecting from Another Computer
To enhance security, the Database Engine of SQL Server 2005 Developer,
Express, and Evaluation Editions cannot be accessed from another computer
when initially installed. This lesson shows you how to enable the protocols,
configure the ports, and configure the Windows Firewall for connecting from
other computers.
This lesson contains the following topics:
a.. Enabling Protocols
b.. Configuring a Fixed Port
c.. Opening Ports in the Firewall
d.. Connecting to the Database Engine from Another Computer
e.. Connecting Using the SQL Server Browser Service
Enabling Protocols
To enhance security, SQL Server 2005 Express Edition Developer Edition and
Evaluation Edition install with only limited network connectivity.
Connections to the Database Engine can be made from tools running the same
computer, but not from other computers. If you are planning to do your
development work on the same computer as the Database Engine, you're done.
Management Studio or Management Studio Express Edition will connect to the
Database Engine using the shared memory protocol, which is already enabled.
If you plan to connect to the Database Engine from another computer, you
must enable a protocol, such as TCP/IP.
How to enable TCP/IP connections from another computer
1. Start SQL Server Surface Area Configuration, and click Surface Area
Configuration for Services.
2. In the Surface Area Configuration for Services and Connections box,
the View by Instance box lists the instances of the Database Engine
installed on the computer. The default instance (an unnamed instance) is
listed as MSSQLSERVER. If you installed a named instance, the name you
provided is listed. SQL Server 2005 Express Edition installs as SQLEXPRESS
unless you changed the name during setup. In the View by Instance box,
expand the instance you wish to configure, expand Database Engine, and then
click Remote Connections.
3. Click Local and remote connections, click Using TCP/IP only, then
click OK and close the tool.
Configuring a Fixed Port
To enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
the Windows Firewall. When SQL Server 2005 Developer, Express, or Evaluation
Edition is running on Windows XP Professional, and you wish to connect to it
from another computer, you must open a communication port in the firewall.
The default instance of the Database Engine listens on port 1433, so you do
not need to configure a fixed port, but named instances including SQL Server
2005 Express Edition listen on dynamic ports. Before you can open a port in
the firewall, you must first configure the Database Engine to listen on a
specific port; otherwise the Database Engine may listen on a different port
each time it is started.
Configure SQL Server to listen on a specific port
1. In SQL Server Configuration Manager, expand SQL Server 2005 Network
Configuration, and then click on the server instance you wish to configure.
2. In the right pane, double-click TCP/IP.
3. In the TCP/IP Properties dialog box, click the IP Addresses tab.
4. In the TCP Port box of the IPAll section, type an available port
number. For this tutorial, we will use 1500.
5. Click OK to close the dialog box, and click OK to the warning that
the service must be restarted.
6. In the left pane, click SQL Server 2005 Services.
7. In the right pane, right-click the instance of SQL Server, and then
click Restart. When the Database Engine restarts, it will listen on port
1500.
Opening Ports in the Firewall
Firewall systems prevent unauthorized access to computer resources. To
enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
Windows Firewall. To connect to SQL Server from another computer, you must
open a port in the firewall.
Important:
Opening ports in your firewall can leave your server exposed to
malicious attacks. Be sure to understand firewall systems before opening
ports. For more information, see Security Considerations for a SQL Server
Installation.
After configuring the Database Engine to use a fixed port, follow the
following instructions to open that port in your Windows Firewall. (You do
not need to configure a fixed port for the default instance, because it is
already fixed on port 1433.)
To open a port in Windows Firewall
1. On the Start menu, click Control Panel.
2. In Control Panel, click Network and Internet Connections, and then
open Windows Firewall.
3. In Windows Firewall, click the Exceptions tab, and then click Add
Port.
4. In the Add a Port dialog box, in the Name box, type SQL Server
<instanceName>.
5. In the Port number box, type the port number of the Database Engine
instance. Use 1433 for the default instance. Type 1500 if you are
configuring a named instance and configured a fixed port in the previous
task. Verify that TCP is selected, and then click OK.
Connecting to the Database Engine from Another Computer
Now that you have configured the Database Engine to listen on a fixed port,
and have opened that port in the firewall, you can connect to SQL Server
from another computer.
When the SQL Server Browser service is running on the server computer, and
when the firewall has opened UDP port 1434, the connection can be made using
the computer name and instance name. To enhance security, our example does
not use the SQL Server Browser service.
To connect to the Database Engine from another computer
1. On a second computer containing the SQL Server 2005 client tools,
log in with an account authorized to connect to SQL Server, and open
Management Studio.
2. In the Connect to Server dialog box, confirm Database Engine in the
Server type box.
3. In the Server name box, type tcp: to specify the protocol, followed
by the computer name, a comma, and the port number. To connect to the
default instance, the port 1433 is implied and can be omitted, so type
tcp:<computer_name>. In our example for a named instance, type
tcp:<computer_name>,1500.
4. In the Authentication box, confirm Window Authentication, and then
click Connect.
Connecting Using the SQL Server Browser Service
The SQL Server Browser service listens for incoming requests for SQL Server
resources and provides information about SQL Server instances installed on
the computer. When the SQL Server Browser service is running, users can
connect to named instances by providing the computer name and instance name,
instead of the computer name and port number. Because SQL Server Browser
receives unauthenticated UDP requests, it is not always turned on during
setup. For a description of the service and an explanation of when it is
turned on, see SQL Server Browser Service.
To use the SQL Server Browser, you must follow the same steps as the
previous task in this lesson, and open UDP port 1434.
This concludes this brief tutorial on basic connectivity. For more
information about configuring server and client connectivity, see Database
Engine Connectivity How-to Topics.
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Willy Verbiest" <willy.verbiest@.telenetnospam.be> wrote in message
news:Oo4ff.51028$Uj3.2801801@.phobos.telenet-ops.be...
> I've just installed sql server 2005 enterprise on my Windows XP
> Professional SP2 machine.
> I can't find a way to connect with it.
> I'm totaly new to SQL Server and have installed it to learn about it.
> I can' t even find out if it is running or not.
> When I do a
> c:>netstat -a
> I can't find the port number 1433 in the list.
> I've checked the services but can't find the name there
> Thanks in advance,
> Willy
>

How to Connect to SQL Server 2005 enterprise version

I've just installed sql server 2005 enterprise on my Windows XP Professional
SP2 machine.
I can't find a way to connect with it.
I'm totaly new to SQL Server and have installed it to learn about it.
I can' t even find out if it is running or not.
When I do a
c:>netstat -a
I can't find the port number 1433 in the list.
I've checked the services but can't find the name there
Thanks in advance,
Willy
This may help. It's a new tutorial I wrote for the coming web release of
Books Online.
Getting Started with the Database Engine
Welcome to the Getting Started with the Database Engine tutorial. This
tutorial is intended for users who are new to SQL Server 2005 and who have
installed Developer, Express, or Evaluation Edition on a computer running
Windows XP Professional Service Pack 1 (SP1).This brief tutorial helps you
get started using the Database Engine.
What You Will Learn
This tutorial shows you how to connect to the Database Engine using SQL
Server Management Studio or Management Studio Express, on both the local
computer and from another computer.
This tutorial is divided into two lessons:
Lesson 1: Connecting to the Database Engine
In this lesson, you will learn how to connect to the Database Engine and
enable additional people to connect.
Lesson 2: Connecting from Another Computer
In this lesson, you will learn how to connect to the Database Engine from a
second computer, including enabling protocols, configuring ports, and
configuring firewall settings.
Requirements
This lesson has no knowledge prerequisites.
Your system must have the following installed to use this tutorial:
a.. Internet Explorer 6.0 or later.
b.. Either SQL Server Management Studio or Management Studio Express.
Lesson 1: Connecting to the Database Engine
When you install the SQL Server 2005 Database Engine, the tools that are
installed depend upon the edition and your setup choices. This lesson
reviews the principal tools, and shows you how to connect and perform a
basic function (authorizing more users).
This lesson contains the following topics:
a.. Tools for Getting Started
b.. Connecting with Management Studio
c.. Authorizing Additional Connections
Tools for Getting Started
The SQL Server 2005 Database Engine ships with a variety of tools. This
topic describes the first tools you will need, and helps you select the
right tool for the job. All tools can be accessed from the Start menu.
Generally, tools such as SQL Server Management Studio are not installed by
default. You must select the tools as part of the client components during
setup. For complete description of the tools described below, search for
them in Books Online. SQL Server 2005 Express Edition contains only a subset
of the tools.
Basic Tools
a.. SQL Server Management Studio is the principal tool for administering
the Database Engine and writing Transact-SQL code. It is hosted in the
Visual Studio shell. It is not included in SQL Server 2005 Express Edition
or SQL Server 2005 Mobile Edition.
b.. SQL Server Management Studio Express is a free, limited version of SQL
Server Management Studio, intended for use with SQL Server 2005 Express
Edition and for users who want the basic features of Management Studio in a
lightweight tool.
c.. SQL Server Surface Area Configuration installs with SQL Server and
lets you enable the server protocols, configure services to start
automatically, and enable some optional features of the Database Engine.
d.. SQL Server Configuration Manager installs with both SQL Server and the
client tools. It lets you enable server protocols, configure protocol
options such as TCP ports, configure server services to start automatically,
and configure client computers to connect in your preferred manner.
Sample Database
SQL Server 2005 includes a sample database called AdventureWorks. This
database is not installed by default. If you wish to experiment with the
AdventureWorks database, you must select it using the Setup program. Most
examples described in Books Online use the AdventureWorks database. For more
information, see Running Setup to Install AdventureWorks Sample Databases
and Samples.
To start SQL Server Management Studio
1. On the Start menu, point to All Programs, point to Microsoft SQL
Server 2005, and then click SQL Server Management Studio.
To start SQL Server Surface Area Configuration or SQL Server Configuration
Manager
1. On the Start menu, point to All Programs, point to Microsoft SQL
Server 2005, point to Configuration Tools, and then click either SQL Server
Surface Area Configuration or SQL Server Configuration Manager.
Connecting with Management Studio
It is easy to connect to the Database Engine from tools running on the same
computer if you know the name of the instance, and if you are connecting as
a member of the Administrators group on the computer. The following
procedures must be performed on the same computer that hosts SQL Server.
To determine the name of the Database Engine instance
1. Log into Windows as a member of the Administrators group, and open
either Management Studio or Management Studio Express Edition.
The Connect to Server dialog box opens.
2. Click Cancel.
3. If Registered Servers is not displayed, on the View menu, click
Registered Servers.
4. With Database Engine selected on the Registered Servers toolbar,
right-click Database Engine, and then click Update Local Server
Registration. All instances of the Database Engine installed on the computer
are displayed. This includes instances of SQL Server 2000. Management Studio
can connect and manage instances of SQL Server 2000 as well as SQL Server
2005. The default instance is unnamed and is shown as the computer name. A
named instance displays as the computer name followed by a backward slash
(\) and then the name of the instance. For SQL Server 2005 Express Edition,
the instance is named <computer_name>\sqlexpress unless the name was changed
during setup.
To verify that the Database Engine is running
1. In Registered Servers, if the name of your instance of SQL Server
has a green dot with a white arrow next to the name, the Database Engine is
running and no further action is necessary.
2. If the name of your instance of SQL Server has a red dot with a
white square next to the name, the Database Engine is stopped. Right-click
the name of the Database Engine, and then click Start. After a confirmation
dialog box, the Database Engine should start and the circle should turn
green.
To connect to the Database Engine
1. On the File menu, click Connect Object Explorer.
The Connect to Server dialog box opens. The Server type box displays the
type that was last used.
2. Select Database Engine.
3. In the Server name box, type the name of the Database Engine
instance.
4. Click Connect.
Authorizing Additional Connections
Now that you have connected to SQL Server as an administrator, one of your
first tasks is to authorize other users to connect. You do this by creating
a login and authorizing that login to access a database as a user. Logins
can be either Windows Authentication logins, which use your Windows
credentials, or SQL Server Authentication logins, which store the
authentication information in SQL Server and are independent of your network
credentials. Use Windows Authentication whenever possible.
Create a Windows Authentication login
1. In the previous task, you connected to the Database Engine using
Management Studio. In Object Explorer, expand your server instance, expand
Security, right-click Logins, and then click New Login.
The Login - New dialog box appears.
2. On the General page, in the Login name box, type a Windows login in
the format <domain>\<login>.
3. In the Default database box, select AdventureWorks if available.
Otherwise select master.
4. On the Server Roles page, if the new login is to be an
administrator, click sysadmin, otherwise leave this blank.
5. On the User Mapping page, select Map for the AdventureWorks
database if it is available. Otherwise select master. Note that the User box
is populated with the login. When closed, the dialog box will create this
user in the database.
6. In the Default Schema box, type dbo to map the login to the
database administrator schema.
7. Accept the default settings for the Securables and Status boxes and
click OK to create the login.
Note:
This is basic information to get you started. SQL Server provides a
rich security environment, and security is obviously an important aspect of
database operations. For more information about security, read the security
sections of Books Online, starting with Security Considerations for
Databases and Database Applications.
Lesson 2: Connecting from Another Computer
To enhance security, the Database Engine of SQL Server 2005 Developer,
Express, and Evaluation Editions cannot be accessed from another computer
when initially installed. This lesson shows you how to enable the protocols,
configure the ports, and configure the Windows Firewall for connecting from
other computers.
This lesson contains the following topics:
a.. Enabling Protocols
b.. Configuring a Fixed Port
c.. Opening Ports in the Firewall
d.. Connecting to the Database Engine from Another Computer
e.. Connecting Using the SQL Server Browser Service
Enabling Protocols
To enhance security, SQL Server 2005 Express Edition Developer Edition and
Evaluation Edition install with only limited network connectivity.
Connections to the Database Engine can be made from tools running the same
computer, but not from other computers. If you are planning to do your
development work on the same computer as the Database Engine, you're done.
Management Studio or Management Studio Express Edition will connect to the
Database Engine using the shared memory protocol, which is already enabled.
If you plan to connect to the Database Engine from another computer, you
must enable a protocol, such as TCP/IP.
How to enable TCP/IP connections from another computer
1. Start SQL Server Surface Area Configuration, and click Surface Area
Configuration for Services.
2. In the Surface Area Configuration for Services and Connections box,
the View by Instance box lists the instances of the Database Engine
installed on the computer. The default instance (an unnamed instance) is
listed as MSSQLSERVER. If you installed a named instance, the name you
provided is listed. SQL Server 2005 Express Edition installs as SQLEXPRESS
unless you changed the name during setup. In the View by Instance box,
expand the instance you wish to configure, expand Database Engine, and then
click Remote Connections.
3. Click Local and remote connections, click Using TCP/IP only, then
click OK and close the tool.
Configuring a Fixed Port
To enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
the Windows Firewall. When SQL Server 2005 Developer, Express, or Evaluation
Edition is running on Windows XP Professional, and you wish to connect to it
from another computer, you must open a communication port in the firewall.
The default instance of the Database Engine listens on port 1433, so you do
not need to configure a fixed port, but named instances including SQL Server
2005 Express Edition listen on dynamic ports. Before you can open a port in
the firewall, you must first configure the Database Engine to listen on a
specific port; otherwise the Database Engine may listen on a different port
each time it is started.
Configure SQL Server to listen on a specific port
1. In SQL Server Configuration Manager, expand SQL Server 2005 Network
Configuration, and then click on the server instance you wish to configure.
2. In the right pane, double-click TCP/IP.
3. In the TCP/IP Properties dialog box, click the IP Addresses tab.
4. In the TCP Port box of the IPAll section, type an available port
number. For this tutorial, we will use 1500.
5. Click OK to close the dialog box, and click OK to the warning that
the service must be restarted.
6. In the left pane, click SQL Server 2005 Services.
7. In the right pane, right-click the instance of SQL Server, and then
click Restart. When the Database Engine restarts, it will listen on port
1500.
Opening Ports in the Firewall
Firewall systems prevent unauthorized access to computer resources. To
enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
Windows Firewall. To connect to SQL Server from another computer, you must
open a port in the firewall.
Important:
Opening ports in your firewall can leave your server exposed to
malicious attacks. Be sure to understand firewall systems before opening
ports. For more information, see Security Considerations for a SQL Server
Installation.
After configuring the Database Engine to use a fixed port, follow the
following instructions to open that port in your Windows Firewall. (You do
not need to configure a fixed port for the default instance, because it is
already fixed on port 1433.)
To open a port in Windows Firewall
1. On the Start menu, click Control Panel.
2. In Control Panel, click Network and Internet Connections, and then
open Windows Firewall.
3. In Windows Firewall, click the Exceptions tab, and then click Add
Port.
4. In the Add a Port dialog box, in the Name box, type SQL Server
<instanceName>.
5. In the Port number box, type the port number of the Database Engine
instance. Use 1433 for the default instance. Type 1500 if you are
configuring a named instance and configured a fixed port in the previous
task. Verify that TCP is selected, and then click OK.
Connecting to the Database Engine from Another Computer
Now that you have configured the Database Engine to listen on a fixed port,
and have opened that port in the firewall, you can connect to SQL Server
from another computer.
When the SQL Server Browser service is running on the server computer, and
when the firewall has opened UDP port 1434, the connection can be made using
the computer name and instance name. To enhance security, our example does
not use the SQL Server Browser service.
To connect to the Database Engine from another computer
1. On a second computer containing the SQL Server 2005 client tools,
log in with an account authorized to connect to SQL Server, and open
Management Studio.
2. In the Connect to Server dialog box, confirm Database Engine in the
Server type box.
3. In the Server name box, type tcp: to specify the protocol, followed
by the computer name, a comma, and the port number. To connect to the
default instance, the port 1433 is implied and can be omitted, so type
tcp:<computer_name>. In our example for a named instance, type
tcp:<computer_name>,1500.
4. In the Authentication box, confirm Window Authentication, and then
click Connect.
Connecting Using the SQL Server Browser Service
The SQL Server Browser service listens for incoming requests for SQL Server
resources and provides information about SQL Server instances installed on
the computer. When the SQL Server Browser service is running, users can
connect to named instances by providing the computer name and instance name,
instead of the computer name and port number. Because SQL Server Browser
receives unauthenticated UDP requests, it is not always turned on during
setup. For a description of the service and an explanation of when it is
turned on, see SQL Server Browser Service.
To use the SQL Server Browser, you must follow the same steps as the
previous task in this lesson, and open UDP port 1434.
This concludes this brief tutorial on basic connectivity. For more
information about configuring server and client connectivity, see Database
Engine Connectivity How-to Topics.
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Willy Verbiest" <willy.verbiest@.telenetnospam.be> wrote in message
news:Oo4ff.51028$Uj3.2801801@.phobos.telenet-ops.be...
> I've just installed sql server 2005 enterprise on my Windows XP
> Professional SP2 machine.
> I can't find a way to connect with it.
> I'm totaly new to SQL Server and have installed it to learn about it.
> I can' t even find out if it is running or not.
> When I do a
> c:>netstat -a
> I can't find the port number 1433 in the list.
> I've checked the services but can't find the name there
> Thanks in advance,
> Willy
>

Monday, March 26, 2012

How to Connect to my Web-SiteSqlServer through Enterprise Manager?

Hi all,

I have Sql Server 2000 installed in my home and also i have a website that works with Sql Server2000 and .Net FrameWork v1.1 ,now i want to know is it possible to connect from
my home SqlServer to Host SqlServer( where my Website resides ) through Enterprise manager or Query Analizer to do some data-manipulation And how?

Thanks in advance.
Regards.

You have to ask for Enterprise Manager access from the hosting company if not they will not offer it. Then you can use the backup and restore wizard to move your databases between servers. Hope this helps.

How to connect to my sql server express,also Pubs and northwind for sql server express

1, I have installed VWD express,sql server 2005 express.I also install management studio and adventureswork db.In the management studio I can able to connect and view adventurework db.
But I can't manage to make a connection string to my db server when connecting to management studio server name is "KAMRANSHAHID\SQLEXPRESS".I wants a connection string with respect to this server.
2,Is there new database for pubs and northwind for sql server 2005.Or they are of old sql server 2000.
I have installed sample databases but can't find script for pubs and northwind nor it install automatically.
I wan't to use tutorial's sample.I have resolved the answer of the question's part 1.
Any Help regarding Part 2 ?????

How to connect to my MSDE 2000 Rel A

Hi,

I only have Framework installed on my machine, and I also installed MSDE 2000 Rel. A, using the following command:
C:\MSDERelA\setup.exe SAPWD="myPass" INSTANCENAME="myXP"

I can see that the service for this app is running. Though, I could not connect to it using oSql command like the following:
osql -S(local)\myXP -E
or
osql -S(local)\myXP -Usa, and supply the password "myPass".

The message was:
[DBMSLPCN]SQL Server does not exist or access denied.
[DBMSLPCN]ConnectionOpen (Connect()).

Any response would be appreciated.



Subi_IHave you tried
osql -L
to verify the instance name?

If that doesn't help you may also want to check out this link|||Hi McMurdo,

Thanks. The command did help to find my database (my initial post was wrong in specifying the instance name).
And the link really helps for managing MSDE without UI tools.

Thanks,



Subi_I

How to Connect to a SQL Server thru a firewall

Hi, Guru,
I have a SQL Server running behind a firewall. I also have a client
installed on my local machine. How should I configure the client to
connect to the server? What port do I need to ask the network/security
admin to open on the firewall? All installation on the server and on the
client are default. I am not familiar with SQL Server, but I have some
common sense. What should I put in the "Server Alias"? The IP of the SQL
Server? What if I run a named instance on the server. Any special
configuration I need to do on Client Network Utility?
If you could show me step by step, it would be great. If you can point me
to some online reference, it will be also great.
Any of you help is appreciated.
ChopinThe default sql server tcp port is 1433. So if you have to connect to a
server behind a firewall, you have to ask the network team to open this
port. To make sure it's working you can run the following command from the
client machine:
telnet servername_or_ip 1433
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"Chopin Hu" <huchopin@.yahoo.com> wrote in message
news:ux7cmyGAEHA.3452@.TK2MSFTNGP11.phx.gbl...
> Hi, Guru,
> I have a SQL Server running behind a firewall. I also have a client
> installed on my local machine. How should I configure the client to
> connect to the server? What port do I need to ask the network/security
> admin to open on the firewall? All installation on the server and on the
> client are default. I am not familiar with SQL Server, but I have some
> common sense. What should I put in the "Server Alias"? The IP of the
SQL
> Server? What if I run a named instance on the server. Any special
> configuration I need to do on Client Network Utility?
> If you could show me step by step, it would be great. If you can point
me
> to some online reference, it will be also great.
> Any of you help is appreciated.
> Chopin
>|||try this
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
Br,
Mark.
"Chopin Hu" <huchopin@.yahoo.com> wrote in message
news:ux7cmyGAEHA.3452@.TK2MSFTNGP11.phx.gbl...
> Hi, Guru,
> I have a SQL Server running behind a firewall. I also have a client
> installed on my local machine. How should I configure the client to
> connect to the server? What port do I need to ask the network/security
> admin to open on the firewall? All installation on the server and on the
> client are default. I am not familiar with SQL Server, but I have some
> common sense. What should I put in the "Server Alias"? The IP of the
SQL
> Server? What if I run a named instance on the server. Any special
> configuration I need to do on Client Network Utility?
> If you could show me step by step, it would be great. If you can point
me
> to some online reference, it will be also great.
> Any of you help is appreciated.
> Chopin
>

How to connect to a dedicated m/c

Hi,
Recently i installed SQL server 2000(EE)on my remote dedicated server( win
2003). I haven't installed ant Service packs. Now the problem is i am not
able to connect to the SQL server either thru Query Analyzer or thru the
application. I have disabled the firewall, still no use. Can anyone help
me.But thru remote desktop, i was able to connect to the server m/c by
putting the ip address .
regards lara
First thing to do is install SP3. SQL2000 RTM isn't supported on
Windows 2003.
David Portas
SQL Server MVP
|||Hi,
I've installed SP3
This is what i get when i run SELECT @.@.Version
"
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
"
I've disabled the firewall, enaled TCP/IP, set default port to 1433. and no
use till now
The same error is diplaying again and again 'Server Msg 17, Level 16, State
1
MS [ODBC Sql Server][DBNETLIB]SQL Server does not exist or access denied'
regards lara
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:1119436842.190857.7930@.o13g2000cwo.googlegrou ps.com...
> First thing to do is install SP3. SQL2000 RTM isn't supported on
> Windows 2003.
> --
> David Portas
> SQL Server MVP
> --
>
|||Hi,
I've installed SP3
This is what i get when i run SELECT @.@.Version
"
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
"
I've disabled the firewall, enaled TCP/IP, set default port to 1433. and no
use till now
The same error is diplaying again and again 'Server Msg 17, Level 16, State
1
MS [ODBC Sql Server][DBNETLIB]SQL Server does not exist or access denied'
regards lara

How to connect to a dedicated m/c

Hi,
Recently i installed SQL server 2000(EE)on my remote dedicated server( win
2003). I haven't installed ant Service packs. Now the problem is i am not
able to connect to the SQL server either thru Query Analyzer or thru the
application. I have disabled the firewall, still no use. Can anyone help
me.But thru remote desktop, i was able to connect to the server m/c by
putting the ip address .
regards laraFirst thing to do is install SP3. SQL2000 RTM isn't supported on
Windows 2003.
David Portas
SQL Server MVP
--|||Hi,
I've installed SP3
This is what i get when i run SELECT @.@.Version
"
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
"
I've disabled the firewall, enaled TCP/IP, set default port to 1433. and no
use till now
The same error is diplaying again and again 'Server Msg 17, Level 16, State
1
MS [ODBC Sql Server][DBNETLIB]SQL Server does not exist or access de
nied'
regards lara
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:1119436842.190857.7930@.o13g2000cwo.googlegroups.com...
> First thing to do is install SP3. SQL2000 RTM isn't supported on
> Windows 2003.
> --
> David Portas
> SQL Server MVP
> --
>|||Hi,
I've installed SP3
This is what i get when i run SELECT @.@.Version
"
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
"
I've disabled the firewall, enaled TCP/IP, set default port to 1433. and no
use till now
The same error is diplaying again and again 'Server Msg 17, Level 16, State
1
MS [ODBC Sql Server][DBNETLIB]SQL Server does not exist or access de
nied'
regards lara