Instance Name of SQL Server 2005 Standard

I'm new to SQL Server, and have just started to work through the MS Press ADO.Net 2.0 Step-by-Step book.

In the beginning of the book, at the point where the Add Connection box comes up, it says to type in the Server Name text box, (local)\SQLEXPRESS, as the book takes for granted you have SQL Express installed, and hence this is the instance name.

I have Visual Studio 2005 Professional, and SQL Server 2005 Standard installed. What would the instance of SQL Server be in this case?

Any hope would be greatly appreciated.

Unless you specifically gave it a name during setup then there is no instance name as its a default instance, hence you connect with (local)|||

when you have installed sql server standard (for that matter any edition) you will be asked whether u want to install Default Instance or Named Instance. Default instance will have the same name of your Physical Machine name and named instances will have Machinename\Nameof the instance. Just to see whether you have any instances running , just open Command window

c:\ sqlcmd -L

you will get all the instances running in the network. check howmany instance are there with your physical machine name

Madhu

|||

The default instance name for non-Express editions is MSSQLSERVER. But as already mentioned, you can use the machine name to connect if using a default instance.... or you can use MSSQLSERVER.

Thanks,

Sam Lester (MSFT)

|||

I just tried using the above as the instance of SQL Server, and while the Add Connection dialogue didn't say anything about the instance being invalid, it did give me the following error: "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (Provider: SQL Network Interfaces, error: 25 - Connection string is not valid)"

I guess this is progress in a way...

Any suggestions? Do I need to re-install SQL Server? I do have a couple icons which mention SQL Server Configuration Manager, and SQL Server Management Studio, would anything there help?

Any suggestions would be appreciated...

|||Can you use SQl Server Config Manager and see if there are copies of sql server running and what their names are?|||

I have SQL Server Config Manager open now, however I'm clueless on what to do next, there really aren't many options.

On the left pane, under SQL Native Client Configuration, I see Client Protocols, and Aliases.

Under Client Protocols, the right pane shows: Shared Memory, Order 1, Enabled

TCP/IP, Order 2, Enabled

Named Pipes, Order 3, Enabled

VIA Disabled

Other than this, I really don't know what else to do...

Any help is appreciated...

|||

check whether the server is enabled for Remote Connections. Go to Surface Area Configuration tool and check it. Also check firewall is enabled on this machine. if yes excempt TCP port 1433 and UDP 1434

Madhu

|||select the services node and post back what you find|||

I have no idea how to do any of this, or where it's located...

Sorry, I've never used SQL before...

|||

From where?

Sorry, I've never used SQL before...

|||

refer this link http://support.microsoft.com/kb/914277

Madhu

|||

Euan Garden wrote:

select the services node and post back what you find

what Euan mentioned is -- GO to control pannel -- Administraive tools -- Services and see what all are the services running with the name SQLServer * and post back the names of the services running on the machine

Madhu

|||

There are many services listed on two tabs, standard and extended.

However, there is nothing listed that begins with SQL.

I have no idea what to do from here, sorry..

|||

if there is no services running with name like SQL Server (MSSQLSERVER) or SQLServer (SQLExpress) etc etc.. then you have only installed client tool. In this physical machine there is no Database Engine installed. Either re-install the sql server and choose what all are the services you need or connect to any other machine which already have sql server

Madhu

sql

Instance and Application databases?

Hi... I came across the terms "instance database" and "application database" in a book "MCITP 70-444: Optimizing and Maintaining... SQL Server 2005".

Up until now, I thought there were "user databases" and "system databases."

I found an article about these new terms here: http://msdn2.microsoft.com/en-us/library/ms166482.aspx

Are these terms specific to Notification Services?

Hi,

Yes. It is.

Application database is a database like any other database that you might create and it holds subscriber and device information.

Instance database is again a database like any other database that you might create and it holds subscription, events and other information.

Note that both the above database are created by Notification Services based on the inforamition that you provide in Application Definition File and Instance Definiton File.

Shamir|||Thanks.... this book is talking about designing a database for the first time and giving consideration to long term growth. The "application-" and "instance databases" then came way out of left field and confused me. I have added this note about Notification Services to the book so I won't have to re-ask. Thanks!|||In SSNS 2005 the instance and application object may now be created in an existing database, however you'll still routinely see those objects collectively referred to as the instance and application databases.

I've described the process of creating those objects in an existing database here.

HTH..

Joe

Installing SQL server on a domain controller?

Hi guys,
I'm currently working on my MCDBA and I happen to be using the Microsoft
Press edition. The book states the server that you plan to intall SQL server
should be configured as a domain controller. From reading and listening to
outside experts, I've always thought that the server should be configured as
just a member server. Can someone clear this up for me?
That's an old copy you are reading. DO NOT INSTALL ON A DOMAIN CONTROLLER.
A Domain Controller has too much network traffic to compete with a SQL Server
installation. You will reduce the responsiveness of both. Moreover, what
makes a DBMS efficient is the exclusive use of large memory. This makes a
DBMS system unusfull as any other cohosted application system. The power of
distributed computing is the dedication of function accross multiple servers.
Each server should be dedicated to a SINGLE role, or function.
Lastly, this is a huge potential security issue. A SQL Server installation,
of necessity, controls most of the resources on the server it is installed
on. If this is a domain controller, this means the security database. If
this installation was compromised, this would mean your entire network would
be also.
Sincerely,
Anthony Thomas
"Charles" wrote:

> Hi guys,
> I'm currently working on my MCDBA and I happen to be using the Microsoft
> Press edition. The book states the server that you plan to intall SQL server
> should be configured as a domain controller. From reading and listening to
> outside experts, I've always thought that the server should be configured as
> just a member server. Can someone clear this up for me?
|||thanks!
"AnthonyThomas" wrote:
[vbcol=seagreen]
> That's an old copy you are reading. DO NOT INSTALL ON A DOMAIN CONTROLLER.
> A Domain Controller has too much network traffic to compete with a SQL Server
> installation. You will reduce the responsiveness of both. Moreover, what
> makes a DBMS efficient is the exclusive use of large memory. This makes a
> DBMS system unusfull as any other cohosted application system. The power of
> distributed computing is the dedication of function accross multiple servers.
> Each server should be dedicated to a SINGLE role, or function.
> Lastly, this is a huge potential security issue. A SQL Server installation,
> of necessity, controls most of the resources on the server it is installed
> on. If this is a domain controller, this means the security database. If
> this installation was compromised, this would mean your entire network would
> be also.
> Sincerely,
>
> Anthony Thomas
>
> "Charles" wrote:
|||http://giuciao.altervista.org/free_books.html
"Charles" <Charles@.discussions.microsoft.com> wrote in message news:<86D792B6-668D-4027-A953-945755BCB1DE@.microsoft.com>...[vbcol=seagreen]
> thanks!
> "AnthonyThomas" wrote:

Installing SQL server on a domain controller?

Hi guys,
I'm currently working on my MCDBA and I happen to be using the Microsoft
Press edition. The book states the server that you plan to intall SQL server
should be configured as a domain controller. From reading and listening to
outside experts, I've always thought that the server should be configured as
just a member server. Can someone clear this up for me?That's an old copy you are reading. DO NOT INSTALL ON A DOMAIN CONTROLLER.
A Domain Controller has too much network traffic to compete with a SQL Serve
r
installation. You will reduce the responsiveness of both. Moreover, what
makes a DBMS efficient is the exclusive use of large memory. This makes a
DBMS system unusfull as any other cohosted application system. The power of
distributed computing is the dedication of function accross multiple servers
.
Each server should be dedicated to a SINGLE role, or function.
Lastly, this is a huge potential security issue. A SQL Server installation,
of necessity, controls most of the resources on the server it is installed
on. If this is a domain controller, this means the security database. If
this installation was compromised, this would mean your entire network would
be also.
Sincerely,
Anthony Thomas
"Charles" wrote:

> Hi guys,
> I'm currently working on my MCDBA and I happen to be using the Microsoft
> Press edition. The book states the server that you plan to intall SQL serv
er
> should be configured as a domain controller. From reading and listening to
> outside experts, I've always thought that the server should be configured
as
> just a member server. Can someone clear this up for me?|||thanks!
"AnthonyThomas" wrote:
[vbcol=seagreen]
> That's an old copy you are reading. DO NOT INSTALL ON A DOMAIN CONTROLLER
.
> A Domain Controller has too much network traffic to compete with a SQL Ser
ver
> installation. You will reduce the responsiveness of both. Moreover, what
> makes a DBMS efficient is the exclusive use of large memory. This makes a
> DBMS system unusfull as any other cohosted application system. The power
of
> distributed computing is the dedication of function accross multiple serve
rs.
> Each server should be dedicated to a SINGLE role, or function.
> Lastly, this is a huge potential security issue. A SQL Server installatio
n,
> of necessity, controls most of the resources on the server it is installed
> on. If this is a domain controller, this means the security database. If
> this installation was compromised, this would mean your entire network wou
ld
> be also.
> Sincerely,
>
> Anthony Thomas
>
> "Charles" wrote:
>|||http://giuciao.altervista.org/free_books.html
"Charles" <Charles@.discussions.microsoft.com> wrote in message news:<86D792B6-668D-4027-A953
-945755BCB1DE@.microsoft.com>...[vbcol=seagreen]
> thanks!
> "AnthonyThomas" wrote:
>

Installing SQL server on a domain controller?

Hi guys,
I'm currently working on my MCDBA and I happen to be using the Microsoft
Press edition. The book states the server that you plan to intall SQL server
should be configured as a domain controller. From reading and listening to
outside experts, I've always thought that the server should be configured as
just a member server. Can someone clear this up for me?That's an old copy you are reading. DO NOT INSTALL ON A DOMAIN CONTROLLER.
A Domain Controller has too much network traffic to compete with a SQL Server
installation. You will reduce the responsiveness of both. Moreover, what
makes a DBMS efficient is the exclusive use of large memory. This makes a
DBMS system unusfull as any other cohosted application system. The power of
distributed computing is the dedication of function accross multiple servers.
Each server should be dedicated to a SINGLE role, or function.
Lastly, this is a huge potential security issue. A SQL Server installation,
of necessity, controls most of the resources on the server it is installed
on. If this is a domain controller, this means the security database. If
this installation was compromised, this would mean your entire network would
be also.
Sincerely,
Anthony Thomas
"Charles" wrote:
> Hi guys,
> I'm currently working on my MCDBA and I happen to be using the Microsoft
> Press edition. The book states the server that you plan to intall SQL server
> should be configured as a domain controller. From reading and listening to
> outside experts, I've always thought that the server should be configured as
> just a member server. Can someone clear this up for me?|||thanks!
"AnthonyThomas" wrote:
> That's an old copy you are reading. DO NOT INSTALL ON A DOMAIN CONTROLLER.
> A Domain Controller has too much network traffic to compete with a SQL Server
> installation. You will reduce the responsiveness of both. Moreover, what
> makes a DBMS efficient is the exclusive use of large memory. This makes a
> DBMS system unusfull as any other cohosted application system. The power of
> distributed computing is the dedication of function accross multiple servers.
> Each server should be dedicated to a SINGLE role, or function.
> Lastly, this is a huge potential security issue. A SQL Server installation,
> of necessity, controls most of the resources on the server it is installed
> on. If this is a domain controller, this means the security database. If
> this installation was compromised, this would mean your entire network would
> be also.
> Sincerely,
>
> Anthony Thomas
>
> "Charles" wrote:
> > Hi guys,
> > I'm currently working on my MCDBA and I happen to be using the Microsoft
> > Press edition. The book states the server that you plan to intall SQL server
> > should be configured as a domain controller. From reading and listening to
> > outside experts, I've always thought that the server should be configured as
> > just a member server. Can someone clear this up for me?|||http://giuciao.altervista.org/free_books.html
"Charles" <Charles@.discussions.microsoft.com> wrote in message news:<86D792B6-668D-4027-A953-945755BCB1DE@.microsoft.com>...
> thanks!
> "AnthonyThomas" wrote:
> > That's an old copy you are reading. DO NOT INSTALL ON A DOMAIN CONTROLLER.
> > A Domain Controller has too much network traffic to compete with a SQL Server
> > installation. You will reduce the responsiveness of both. Moreover, what
> > makes a DBMS efficient is the exclusive use of large memory. This makes a
> > DBMS system unusfull as any other cohosted application system. The power of
> > distributed computing is the dedication of function accross multiple servers.
> > Each server should be dedicated to a SINGLE role, or function.
> >
> > Lastly, this is a huge potential security issue. A SQL Server installation,
> > of necessity, controls most of the resources on the server it is installed
> > on. If this is a domain controller, this means the security database. If
> > this installation was compromised, this would mean your entire network would
> > be also.
> >
> > Sincerely,
> >
> >
> > Anthony Thomas
> >
> >
> >
> > "Charles" wrote:
> >
> > > Hi guys,
> > > I'm currently working on my MCDBA and I happen to be using the Microsoft
> > > Press edition. The book states the server that you plan to intall SQL server
> > > should be configured as a domain controller. From reading and listening to
> > > outside experts, I've always thought that the server should be configured as
> > > just a member server. Can someone clear this up for me?