attempting to connect locally

#41

If nothing is listed, then SQL Server 2005 is not installed. Perhaps you
installed SQL Server 2005 tools, but not the Database Engine?
Perhaps you installed SQL Server 2000?
Try this, On the Start menu click Run, type services.msc, and then click OK.
This will open the services applet in Microsoft Management Console.
If you have SQL Server 2000, it will be listed under M. Something like
Microsoft SQL Server, or MSSQLSERVER.
If you have SQL Server 2005, it will be listed under S as SQL Server.
If nothing, then you have to run setup to install SQL Server.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"srain001" <srain001 (AT) discussions (DOT) microsoft.com> wrote

Quote:

Hi,

Sorry, I should've been more clear: There is actually nothing listed in
the
in SQL server 2005 services in configuration manager. That's my dilemma.
Where can I go to get something listed? Thanx.

Srain

"Ekrem Önsoy" wrote:

To be able to connect to an instance of SQL Server, you should run its
core
service at least. It's core service's name looks like this in CM if it's
a
Default Instance: "SQL Server (MSSQLSERVER)" and if it's a Named Instance
then it looks like this: "SQL Server (<your_named_instance_name>)"

So in Configuration Manager, right click on the SQL Server service and
click
Start to start the service. If somehow it does not start (probably
because
of the insufficient or incorrect account information) then tell us what
the
error message says.

--
Ekrem Önsoy

"srain001" <srain001 (AT) discussions (DOT) microsoft.com> wrote in message
news:A607B35F-4466-40DF-BBD4-2FA8C501E539 (AT) microsoft (DOT) com...
Hi,

I've gone into the Config manager and selected SQL server services.
There
is nothing running. How can I activate a server instance?

Thanx!
srain

"Ekrem Önsoy" wrote:

There are two types of SQL Server instances. One is the Default
Instance
which could be only one on each OS and the other is Named Instances.
Default
Instance' s name is the name of your Computer and you assign the name
of
the
Named Instance in SQL Server Setup.

Ensure you have an installed and running SQL Server Instance first
then
try
to connect it...

To see the SQL Server services, go to Start\Programs\Microsoft SQL
Server
2005\Configuration Tools\SQL Server Configuration Manager.

Click on "SQL Server 2005 Services" from the left pane and see the SQL
Server services from the right pane if you have installed any. If
there
is
any SQL Server service, then ensure it's running and up. After that,
try
to
connect that instance.

--
Ekrem Önsoy

"srain001" <srain001 (AT) discussions (DOT) microsoft.com> wrote in message
news:B42BBA7A-02D9-49CD-974C-EEBDA42C3099 (AT) microsoft (DOT) com...
Hello,

I am running SQL server on my machine for the first time and have
very
little experiance with this application. I am running this app on
my
machine
only (the client) and am attempting to log on using the Management
Studio.
Unfortunately, the application does not seem to recognize my
computer
identity. As I understand it, if I am not connected to a server
machine,
then the SQL application should recognize my client machine as the
local
server, right? Unfortunately, I cannot connect. I must be doing
something
wrong.

Here are the steps I have taken:

1- Installed SQL with analysis services
2- accessed SQL Server Management Studio
3- logon screen appears: Server Type = Database Engine, Server Name
=
(blank), Authentication = Windows Authentication.
4- The scoll-down list in Server Name is also blank so I located my
computer
identity and entered it. I was unable to connect.

Please help!

srain

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

attempting to connect locally

microsoft.public.sqlserver.clients microsoft.public.sqlserver.clients

Re: attempting to connect locally - 04-10-2008 , 08:58 AM