Northwind and pubs default login/password ?

Hello,

What are the default login/password to access pubs and northwind databases ?
I remember the login = "sa", but nothing about the password.

Thanks

EricEricP (eric.piquot@.wanadoo.fr) writes:
> What are the default login/password to access pubs and northwind
> databases ? I remember the login = "sa", but nothing about the password.

Password are associated with logins and not with databases. And logins
are associated with servers and not with databases.

The default password for "sa" used to be blank, but hopefully this has
been changed on your server.

You can also log with in with Windows authentication. In this case you
don't provide a password, since you are already logged into Windows.
(Unless you are using Win 98 or somesuch.)

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Sorry for my badly English,

Erland Sommarskog a crit :
> EricP (eric.piquot@.wanadoo.fr) writes:
>>What are the default login/password to access pubs and northwind
>>databases ? I remember the login = "sa", but nothing about the password.
>
> Password are associated with logins and not with databases. And logins
> are associated with servers and not with databases.
I don't understand:
3 databases A, B, C on a server.
Hope one distinct (login,password) per database for the same user.
> The default password for "sa" used to be blank, but hopefully this has
> been changed on your server.
> You can also log with in with Windows authentication. In this case you
> don't provide a password, since you are already logged into Windows.
> (Unless you are using Win 98 or somesuch.)
Right

Thanks|||EricP (eric.piquot@.wanadoo.fr) writes:
> I don't understand:
> 3 databases A, B, C on a server.
> Hope one distinct (login,password) per database for the same user.

Not sure that I understand where you heading at.

But here is how security works in SQL Server. On server level you have
logins. A login can be an SQL login or a Windows login. SQL logins have
passwords, Winodws login have not (in SQL Server; they have in Windows
of course). A login can be associated with a user in a database. Most
often login name and user name are the same, but not there is no law
that requires this. Thus, once a person have logged into SQL Server,
he can access several databases, but if he is not added as user in
a database, he has no permission to it. (I'm bere overlooking the fact
that he may own a database ae well.)

If I understand you correctly, you want the same physical person have
three different (login, password) for three different databases. In
such case this person needs to have three different logins in SQL Server,
and this means that you need to use SQL logins, or else the person will
have to change between different Windows users.

There is one more alternative, and that is application roles. With an
application role you can get access to objects in a data to which
permissions have been granted to that role. To get access to an application
role, you need to supply the password. The typical use of an
application role is that you issue sp_setapprole from the application,
and the password is embedded in the application somewhere; thus the
users never supply it, or even know about it.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||
Erland Sommarskog a crit :
> If I understand you correctly, you want the same physical person have
> three different (login, password) for three different databases. In
> such case this person needs to have three different logins in SQL Server,
> and this means that you need to use SQL logins, or else the person will
> have to change between different Windows users.

That's quiet.
Thankssql

Non-queried default values not working

This is driving me crazy. I can't get non-queried default values to
work with non-queried string report parameters. I'm using Reporting
Services 2000. Here's a test case: I have a simple Report Parameter: a
string, called "Color". It has three non-queried label-value pairs:
Red-red, Green-green, Blue-blue. I then try to define a default
non-queried value of green. Run the report, it always says "Select a
value". If I change the label-values to single-digit values, like
this: Red-1, Green-2, Blue-3, and set the default value to 2, then
Green comes up as the selected value (which is what I want). But I
cannot use a string for the value - it never matches. I've also tried
two-digit numbers: Red-11, Green-22, Blue-33, and used 22 as the
default. Comes up with "Select a value".
Can you not use strings as default values?Found the answer myself. Yes, you can use strings as default values,
as you would expect. Everything worked great in the Preview pane of
Visual Studio (the defaults would show properly) but when I put the
report on the report server, the dropdowns would say "Select a value".
To fix it, I had to completely delete the report from the server, and
upload a brand new copy of the RDL file. It did not work to simply use
the "Update" option in the Report Properties web page on the server.
It would update the report (i.e., I could see other changes I made) but
for some reason, the parameters would not work properly until I
completed deleted the report and uploaded it again. Go figure.

Non-Cluster Index Primary Key

I inherited a SQL Server 2000 database that has performance issues. I
noticed the primary keys are set up as non-cluster indexes.
By default the table primary key is created as cluster indexes. Could this
cause a database performance problems if these are large tables and access
often.
If the table were set up with the primary key as a non-cluster index?
Thanks,There is no requirement that the PK (or any index for that matter) be
clustered. But it is recommended that every table have a clustered index.
Which one depends on how you are using it. You have to narrow down the
performance issues much more before anyone can answer this question. See if
these help:
http://www.microsoft.com/sql/techin.../perftuning.asp
Performance WP's
http://www.swynk.com/friends/vandenberg/perfmonitor.asp Perfmon counters
http://www.sql-server-performance.c...mance_audit.asp
Hardware Performance CheckList
http://www.sql-server-performance.c...rmance_tips.asp
SQL 2000 Performance tuning tips
http://www.support.microsoft.com/?id=q224587 Troubleshooting App
Performance
http://msdn.microsoft.com/library/d.../>
on_24u1.asp
Disk Monitoring
Andrew J. Kelly SQL MVP
"Joe K." <JoeK@.discussions.microsoft.com> wrote in message
news:17DC89CC-A77A-486E-BADF-60AC39B5A973@.microsoft.com...
> I inherited a SQL Server 2000 database that has performance issues. I
> noticed the primary keys are set up as non-cluster indexes.
> By default the table primary key is created as cluster indexes. Could this
> cause a database performance problems if these are large tables and access
> often.
> If the table were set up with the primary key as a non-cluster index?
>
> Thanks,

Non-Cluster Index Primary Key

I inherited a SQL Server 2000 database that has performance issues. I
noticed the primary keys are set up as non-cluster indexes.
By default the table primary key is created as cluster indexes. Could this
cause a database performance problems if these are large tables and access
often.
If the table were set up with the primary key as a non-cluster index?
Thanks,There is no requirement that the PK (or any index for that matter) be
clustered. But it is recommended that every table have a clustered index.
Which one depends on how you are using it. You have to narrow down the
performance issues much more before anyone can answer this question. See if
these help:
http://www.microsoft.com/sql/techinfo/administration/2000/perftuning.asp
Performance WP's
http://www.swynk.com/friends/vandenberg/perfmonitor.asp Perfmon counters
http://www.sql-server-performance.com/sql_server_performance_audit.asp
Hardware Performance CheckList
http://www.sql-server-performance.com/best_sql_server_performance_tips.asp
SQL 2000 Performance tuning tips
http://www.support.microsoft.com/?id=q224587 Troubleshooting App
Performance
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_perfmon_24u1.asp
Disk Monitoring
--
Andrew J. Kelly SQL MVP
"Joe K." <JoeK@.discussions.microsoft.com> wrote in message
news:17DC89CC-A77A-486E-BADF-60AC39B5A973@.microsoft.com...
> I inherited a SQL Server 2000 database that has performance issues. I
> noticed the primary keys are set up as non-cluster indexes.
> By default the table primary key is created as cluster indexes. Could this
> cause a database performance problems if these are large tables and access
> often.
> If the table were set up with the primary key as a non-cluster index?
>
> Thanks,

Non-Cluster Index Primary Key

I inherited a SQL Server 2000 database that has performance issues. I
noticed the primary keys are set up as non-cluster indexes.
By default the table primary key is created as cluster indexes. Could this
cause a database performance problems if these are large tables and access
often.
If the table were set up with the primary key as a non-cluster index?
Thanks,
There is no requirement that the PK (or any index for that matter) be
clustered. But it is recommended that every table have a clustered index.
Which one depends on how you are using it. You have to narrow down the
performance issues much more before anyone can answer this question. See if
these help:
http://www.microsoft.com/sql/techinf...perftuning.asp
Performance WP's
http://www.swynk.com/friends/vandenberg/perfmonitor.asp Perfmon counters
http://www.sql-server-performance.co...ance_audit.asp
Hardware Performance CheckList
http://www.sql-server-performance.co...mance_tips.asp
SQL 2000 Performance tuning tips
http://www.support.microsoft.com/?id=q224587 Troubleshooting App
Performance
http://msdn.microsoft.com/library/de...rfmon_24u1.asp
Disk Monitoring
Andrew J. Kelly SQL MVP
"Joe K." <JoeK@.discussions.microsoft.com> wrote in message
news:17DC89CC-A77A-486E-BADF-60AC39B5A973@.microsoft.com...
> I inherited a SQL Server 2000 database that has performance issues. I
> noticed the primary keys are set up as non-cluster indexes.
> By default the table primary key is created as cluster indexes. Could this
> cause a database performance problems if these are large tables and access
> often.
> If the table were set up with the primary key as a non-cluster index?
>
> Thanks,

Non-Admin user can't create a linked report in My Reports...

A Non-Admin user can't create a linked report in his My Reports folder.
Reporting Services is set up with My Reports enabled with the default tasks
assigned to the My Reports role (this includes Create linked reports). This
same user can create sub-folders but not linked reports.
----
aspnet_wp!library!164!10/07/2004-17:42:44:: i INFO: Call to
CreateLinkedReport( '20041007 1742 SimpleReport', '/My
Reports/Submitted/Test', '/Standard Reports/Test/SimpleReport',
'Microsoft.ReportingServices.Library.Soap.Property[]' )
aspnet_wp!library!164!10/07/2004-17:42:44:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The
permissions granted to user 'LABTM\RSFinancialAnalyst' are insufficient for
performing this operation., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The
permissions granted to user 'LABTM\RSFinancialAnalyst' are insufficient for
performing this operation.Does the user have Read Properties permission to the report /Standard
Reports/Test/SimpleReport?
-Lukasz|||I discovered the problem... The Browser Role is not associated with the
"Create linked reports" task by default. Once I assigned the Create linked
reports task to the Browser Role the non-admin user could create linked
reports.
Thanks for the hint Lukasz.
Garry Lenz
"Garry Lenz" <glenz@.thoughtmill.com> wrote in message
news:%231hAadLrEHA.2136@.TK2MSFTNGP14.phx.gbl...
> A Non-Admin user can't create a linked report in his My Reports folder.
> Reporting Services is set up with My Reports enabled with the default
tasks
> assigned to the My Reports role (this includes Create linked reports).
This
> same user can create sub-folders but not linked reports.
> ----
> aspnet_wp!library!164!10/07/2004-17:42:44:: i INFO: Call to
> CreateLinkedReport( '20041007 1742 SimpleReport', '/My
> Reports/Submitted/Test', '/Standard Reports/Test/SimpleReport',
> 'Microsoft.ReportingServices.Library.Soap.Property[]' )
> aspnet_wp!library!164!10/07/2004-17:42:44:: e ERROR: Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException:
The
> permissions granted to user 'LABTM\RSFinancialAnalyst' are insufficient
for
> performing this operation., ;
> Info:
> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException:
The
> permissions granted to user 'LABTM\RSFinancialAnalyst' are insufficient
for
> performing this operation.
>

Non standard port - non default instance

Hi all,
I'm trying to create a subscription for a merge replication on a sql
server mobile 2005 based application.
The publisher is on a intranet, listening on port 9091 and with a named
instance.
The merge agent is in a DMZ with port 9091 open for inbound/outbound TCP
traffic to the intranet.
Problem:
when I try to synchronize I receive the "SQL Server does not exists" error.
My subscription has the following setup:
Publisher = "ServerName\InstanceName";
PublisherNetwork = NetworkType.TcpIpSockets;
PublisherAddress = "10.xxx.xxx.xxx,9091";
PublisherDatabase = "DatabaseName";
PublisherSecurityMode = SecurityType.DBAuthentication;
PublisherLogin = "name";
PublisherPassword = "pwd";
name/pwd user has correct priviledges non publisher database.
I can connect via SQL Client to the database from the machine in DMZ.
In my (many) tries, I also created an alias on the DMZ client and used
that for the Publisher property at the subscriber.
Nothing worked.
I'm finishing options...
Cl@. ha scritto:

> Problem:
> when I try to synchronize I receive the "SQL Server does not exists" error.
I solved opening 1434 udp port.
Question is: why sql client can connect without 1434 port open and the
merge agent can't?

non default port - client cannot connect

I have changed the default port away from 1433 on sql server 2005. Now I
cannot connect from pc. What do I need to change on the client pc?
Thanks
Connect by adding a comma and port number after machine name, like:
machinename,1456
Or use cliconfg.exe to add an alias and specify the port number in that alias.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"guest5" <guest5@.discussions.microsoft.com> wrote in message
news:0A38D0A1-E40F-4A97-93D6-5C288E867802@.microsoft.com...
>I have changed the default port away from 1433 on sql server 2005. Now I
> cannot connect from pc. What do I need to change on the client pc?
> Thanks

non default port - client cannot connect

I have changed the default port away from 1433 on sql server 2005. Now I
cannot connect from pc. What do I need to change on the client pc?
ThanksConnect by adding a comma and port number after machine name, like:
machinename,1456
Or use cliconfg.exe to add an alias and specify the port number in that alia
s.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"guest5" <guest5@.discussions.microsoft.com> wrote in message
news:0A38D0A1-E40F-4A97-93D6-5C288E867802@.microsoft.com...
>I have changed the default port away from 1433 on sql server 2005. Now I
> cannot connect from pc. What do I need to change on the client pc?
> Thanks

non default port - client cannot connect

I have changed the default port away from 1433 on sql server 2005. Now I
cannot connect from pc. What do I need to change on the client pc?
ThanksConnect by adding a comma and port number after machine name, like:
machinename,1456
Or use cliconfg.exe to add an alias and specify the port number in that alias.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"guest5" <guest5@.discussions.microsoft.com> wrote in message
news:0A38D0A1-E40F-4A97-93D6-5C288E867802@.microsoft.com...
>I have changed the default port away from 1433 on sql server 2005. Now I
> cannot connect from pc. What do I need to change on the client pc?
> Thanks

Non default port

I am using SQL 2005 and have multiple instances installed on multiple
servers. None are on the default port. When I connect to box 01
without specifying the port in the connection string, it connects.
But on box 02, it will only connect to the instance if I specify the
port name. Is this because it will only connect to the default
instance without specifying a port? or is there something else I need
to have setup on box 02 to make this work?
thanks in advance
> Is this because it will only connect to the default
> instance without specifying a port? or is there something else I need
> to have setup on box 02 to make this work?
Check to ensure the SQL Browser service is running as Tibor suggested.
Another possible cause is that UDP port 1434 is blocked.
When you connect to the default instance, TCP port 1433 is used by default.
When you connect to a named instance without a specifying a port, the client
requests a list of the named instances and corresponding ports via UDP port
1434 (this is the SQL Browser service). The client then determines the
named instance port.
Hope this helps.
Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/
"Victag" <miketaggart@.gmail.com> wrote in message
news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>I am using SQL 2005 and have multiple instances installed on multiple
> servers. None are on the default port. When I connect to box 01
> without specifying the port in the connection string, it connects.
> But on box 02, it will only connect to the instance if I specify the
> port name. Is this because it will only connect to the default
> instance without specifying a port? or is there something else I need
> to have setup on box 02 to make this work?
> thanks in advance
|||On Mar 13, 4:26Xam, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> Check to ensure the SQL Browser service is running as Tibor suggested.
> Another possible cause is that UDP port 1434 is blocked.
> When you connect to the default instance, TCP port 1433 is used by default..
> When you connect to a named instance without a specifying a port, the client
> requests a list of the named instances and corresponding ports via UDP port
> 1434 (this is the SQL Browser service). XThe client then determines the
> named instance port.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVPhttp://weblogs.sqlteam.com/dang/
> "Victag" <miketagg...@.gmail.com> wrote in message
> news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>
>
> - Show quoted text -
Thanks folks! I have checked and the Browser service is disabled on
both boxes (event he working one), so I could try turning it on, but I
would rather explain/understand what the difference is between these
boxes. I have also confirmed that no ports are blocked at all. Any
other suggestions?
|||Hi,
You can access named instances (if you know port number) in this way:
tcp:server_name,port_number
Regards,
anxcomp
|||On Mar 13, 11:12Xam, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> <<Thanks folks! XI have checked and the Browser service is disabled on
> both boxes (event he working one), so I could try turning it on, but I
> would rather explain/understand what the difference is between these
> boxes. XI have also confirmed that no ports are blocked at all. XAny
> other suggestions?>>
> We can only explain how things work:
> When you connect to a default instance (no backslash and instance name), the data access components
> will connect to port 1433. The SQL Server service by default listens to 1433 for a default instance
> (well-known port).
> The port number for a named instance is determined dynamically the first time you start the
> instance. SQL Server asks Windows for an available port, uses it and stores the port number in the
> registry (as you can see using SQL Server Configuration Manager). It will try to use the same port
> number on subsequent start-ups.
> If you from the client app only specify machine name/IP backslash instancename, then you need some
> component to translate this instance name to a port number. That componentis SQL Server Browser
> service. The client data access components connects to the SSB service using port 1434 UDP and
> passes the instance name, and the SSB service returns the port number. Youcan also from the client
> app specify machine/IP comma portnumber, so there would now be no use for the SSB service. SQL
> Server 2000 didn't come with an SSB service so for 2000 the database engine did this job (listening
> on port 1434).
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "Victag" <miketagg...@.gmail.com> wrote in message
> news:bee0415f-6523-45e7-9d46-ad9a01846809@.d62g2000hsf.googlegroups.com...
> On Mar 13, 4:26 am, "Dan Guzman" <guzma...@.nospam-
>
>
> online.sbcglobal.net> wrote:
>
>
>
>
>
> Thanks folks! XI have checked and the Browser service is disabled on
> both boxes (event he working one), so I could try turning it on, but I
> would rather explain/understand what the difference is between these
> boxes. XI have also confirmed that no ports are blocked at all. XAny
> other suggestions... Hide quoted text -
> - Show quoted text -
Thanks again. I have made progress and found that the boxes that are
not working have many client aliases created on them, some of which
appear to be invalid. When I deleted the aliases that did not exist
on the server that is working, it fixed them. So now that I know how
to fix it, I am curious to know how these bad aliases got created
since we did not create them manually.
|||"Victag" wrote:

>I am curious to know how these bad aliases got created
> since we did not create them manually.
Did you install Visio? For example Visio installation process create for me
some alias. I have to delete it manually.
Regards,
anxcomp

Non default port

I am using SQL 2005 and have multiple instances installed on multiple
servers. None are on the default port. When I connect to box 01
without specifying the port in the connection string, it connects.
But on box 02, it will only connect to the instance if I specify the
port name. Is this because it will only connect to the default
instance without specifying a port? or is there something else I need
to have setup on box 02 to make this work?
thanks in advance :)See if the SQL Server Browser service is started on box 02.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Victag" <miketaggart@.gmail.com> wrote in message
news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>I am using SQL 2005 and have multiple instances installed on multiple
> servers. None are on the default port. When I connect to box 01
> without specifying the port in the connection string, it connects.
> But on box 02, it will only connect to the instance if I specify the
> port name. Is this because it will only connect to the default
> instance without specifying a port? or is there something else I need
> to have setup on box 02 to make this work?
> thanks in advance :)|||> Is this because it will only connect to the default
> instance without specifying a port? or is there something else I need
> to have setup on box 02 to make this work?
Check to ensure the SQL Browser service is running as Tibor suggested.
Another possible cause is that UDP port 1434 is blocked.
When you connect to the default instance, TCP port 1433 is used by default.
When you connect to a named instance without a specifying a port, the client
requests a list of the named instances and corresponding ports via UDP port
1434 (this is the SQL Browser service). The client then determines the
named instance port.
--
Hope this helps.
Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/
"Victag" <miketaggart@.gmail.com> wrote in message
news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>I am using SQL 2005 and have multiple instances installed on multiple
> servers. None are on the default port. When I connect to box 01
> without specifying the port in the connection string, it connects.
> But on box 02, it will only connect to the instance if I specify the
> port name. Is this because it will only connect to the default
> instance without specifying a port? or is there something else I need
> to have setup on box 02 to make this work?
> thanks in advance :)|||On Mar 13, 4:26=A0am, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> > Is this because it will only connect to the default
> > instance without specifying a port? or is there something else I need
> > to have setup on box 02 to make this work?
> Check to ensure the SQL Browser service is running as Tibor suggested.
> Another possible cause is that UDP port 1434 is blocked.
> When you connect to the default instance, TCP port 1433 is used by default=.
> When you connect to a named instance without a specifying a port, the clie=nt
> requests a list of the named instances and corresponding ports via UDP por=t
> 1434 (this is the SQL Browser service). =A0The client then determines the
> named instance port.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVPhttp://weblogs.sqlteam.com/dang/
> "Victag" <miketagg...@.gmail.com> wrote in message
> news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>
> >I am using SQL 2005 and have multiple instances installed on multiple
> > servers. =A0None are on the default port. =A0When I connect to box 01
> > without specifying the port in the connection string, it connects.
> > But on box 02, it will only connect to the instance if I specify the
> > port name. =A0Is this because it will only connect to the default
> > instance without specifying a port? or is there something else I need
> > to have setup on box 02 to make this work?
> > thanks in advance :)- Hide quoted text -
> - Show quoted text -
Thanks folks! I have checked and the Browser service is disabled on
both boxes (event he working one), so I could try turning it on, but I
would rather explain/understand what the difference is between these
boxes. I have also confirmed that no ports are blocked at all. Any
other suggestions?|||<<Thanks folks! I have checked and the Browser service is disabled on
both boxes (event he working one), so I could try turning it on, but I
would rather explain/understand what the difference is between these
boxes. I have also confirmed that no ports are blocked at all. Any
other suggestions?>>
We can only explain how things work:
When you connect to a default instance (no backslash and instance name), the data access components
will connect to port 1433. The SQL Server service by default listens to 1433 for a default instance
(well-known port).
The port number for a named instance is determined dynamically the first time you start the
instance. SQL Server asks Windows for an available port, uses it and stores the port number in the
registry (as you can see using SQL Server Configuration Manager). It will try to use the same port
number on subsequent start-ups.
If you from the client app only specify machine name/IP backslash instancename, then you need some
component to translate this instance name to a port number. That component is SQL Server Browser
service. The client data access components connects to the SSB service using port 1434 UDP and
passes the instance name, and the SSB service returns the port number. You can also from the client
app specify machine/IP comma portnumber, so there would now be no use for the SSB service. SQL
Server 2000 didn't come with an SSB service so for 2000 the database engine did this job (listening
on port 1434).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Victag" <miketaggart@.gmail.com> wrote in message
news:bee0415f-6523-45e7-9d46-ad9a01846809@.d62g2000hsf.googlegroups.com...
On Mar 13, 4:26 am, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> > Is this because it will only connect to the default
> > instance without specifying a port? or is there something else I need
> > to have setup on box 02 to make this work?
> Check to ensure the SQL Browser service is running as Tibor suggested.
> Another possible cause is that UDP port 1434 is blocked.
> When you connect to the default instance, TCP port 1433 is used by default.
> When you connect to a named instance without a specifying a port, the client
> requests a list of the named instances and corresponding ports via UDP port
> 1434 (this is the SQL Browser service). The client then determines the
> named instance port.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVPhttp://weblogs.sqlteam.com/dang/
> "Victag" <miketagg...@.gmail.com> wrote in message
> news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>
> >I am using SQL 2005 and have multiple instances installed on multiple
> > servers. None are on the default port. When I connect to box 01
> > without specifying the port in the connection string, it connects.
> > But on box 02, it will only connect to the instance if I specify the
> > port name. Is this because it will only connect to the default
> > instance without specifying a port? or is there something else I need
> > to have setup on box 02 to make this work?
> > thanks in advance :)- Hide quoted text -
> - Show quoted text -
Thanks folks! I have checked and the Browser service is disabled on
both boxes (event he working one), so I could try turning it on, but I
would rather explain/understand what the difference is between these
boxes. I have also confirmed that no ports are blocked at all. Any
other suggestions?|||Hi,
You can access named instances (if you know port number) in this way:
tcp:server_name,port_number
--
Regards,
anxcomp|||On Mar 13, 11:12=A0am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> <<Thanks folks! =A0I have checked and the Browser service is disabled on
> both boxes (event he working one), so I could try turning it on, but I
> would rather explain/understand what the difference is between these
> boxes. =A0I have also confirmed that no ports are blocked at all. =A0Any
> other suggestions?>>
> We can only explain how things work:
> When you connect to a default instance (no backslash and instance name), t=he data access components
> will connect to port 1433. The SQL Server service by default listens to 14=33 for a default instance
> (well-known port).
> The port number for a named instance is determined dynamically the first t=ime you start the
> instance. SQL Server asks Windows for an available port, uses it and store=s the port number in the
> registry (as you can see using SQL Server Configuration Manager). It will =try to use the same port
> number on subsequent start-ups.
> If you from the client app only specify machine name/IP backslash instance=name, then you need some
> component to translate this instance name to a port number. That component= is SQL Server Browser
> service. The client data access components connects to the SSB service usi=ng port 1434 UDP and
> passes the instance name, and the SSB service returns the port number. You= can also from the client
> app specify machine/IP comma portnumber, so there would now be no use for =the SSB service. SQL
> Server 2000 didn't come with an SSB service so for 2000 the database engin=e did this job (listening
> on port 1434).
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph=
ttp://sqlblog.com/blogs/tibor_karaszi
> "Victag" <miketagg...@.gmail.com> wrote in message
> news:bee0415f-6523-45e7-9d46-ad9a01846809@.d62g2000hsf.googlegroups.com...
> On Mar 13, 4:26 am, "Dan Guzman" <guzma...@.nospam-
>
>
> online.sbcglobal.net> wrote:
> > > Is this because it will only connect to the default
> > > instance without specifying a port? or is there something else I need
> > > to have setup on box 02 to make this work?
> > Check to ensure the SQL Browser service is running as Tibor suggested.
> > Another possible cause is that UDP port 1434 is blocked.
> > When you connect to the default instance, TCP port 1433 is used by defau=lt.
> > When you connect to a named instance without a specifying a port, the cl=ient
> > requests a list of the named instances and corresponding ports via UDP p=ort
> > 1434 (this is the SQL Browser service). The client then determines the
> > named instance port.
> > --
> > Hope this helps.
> > Dan Guzman
> > SQL Server MVPhttp://weblogs.sqlteam.com/dang/
> > "Victag" <miketagg...@.gmail.com> wrote in message
> >news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...=
> > >I am using SQL 2005 and have multiple instances installed on multiple
> > > servers. None are on the default port. When I connect to box 01
> > > without specifying the port in the connection string, it connects.
> > > But on box 02, it will only connect to the instance if I specify the
> > > port name. Is this because it will only connect to the default
> > > instance without specifying a port? or is there something else I need
> > > to have setup on box 02 to make this work?
> > > thanks in advance :)- Hide quoted text -
> > - Show quoted text -
> Thanks folks! =A0I have checked and the Browser service is disabled on
> both boxes (event he working one), so I could try turning it on, but I
> would rather explain/understand what the difference is between these
> boxes. =A0I have also confirmed that no ports are blocked at all. =A0Any
> other suggestions... Hide quoted text -
> - Show quoted text -
Thanks again. I have made progress and found that the boxes that are
not working have many client aliases created on them, some of which
appear to be invalid. When I deleted the aliases that did not exist
on the server that is working, it fixed them. So now that I know how
to fix it, I am curious to know how these bad aliases got created
since we did not create them manually.|||"Victag" wrote:
>I am curious to know how these bad aliases got created
> since we did not create them manually.
Did you install Visio? For example Visio installation process create for me
some alias. I have to delete it manually.
Regards,
anxcomp