How do I create an instance of sql server 2005

Question

How do I create an instance of sql server 2005

Lara L

Grasshopper

Points: 17
More actions
July 2, 2006 at 10:09 am

#169453

I am trying to install the evaluation copy of sql server 2005 which I have done to a point but I can't seem to be able to create an instance of sql server 2005 and keep getting an error No server connection.
Please help.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Jens Süßmeyer SSC Enthusiast Points: 165 More actions · Answer 1

Instances are created during the setup process / install, if you don´t have any instance created (look in the Service Control manager SCM if any SQL Server (MSSLQSERVER) services (or other names in the parant. for other named instances) were installed.

HTH, Jens Suessmeyer.

---

http://www.sqlserver2005.de

---

Chad Slagle SSC Veteran Points: 200 More actions · Answer 2

I'm assuming you have the client installed. I'm guessing you cannot access this server using the object explorer, or register the server using the SQL Server Management Studio.. If you haven't done so, install the client.. It's pretty self explanitory for the most part.

Otherwise..

1) You should try to ping the server using the server name (not the IP) to see if you are connecting to the server. (eliminating the networking issues)

2) Check with your network geeks to see if port 1433 can be used to connect to that server. Sometimes, McAfee for example, uses a port blocker to combat worms and block certain ports and sometimes that is on the list.

3) Also, use the SQL Server Configuration Manager to make sure that you are able to use the protocol you intend to use to connect to the SQL Server 2005 instance you created. You will need to look directly on the server.

In the left hand column you will find three selections:

a) SQL Server 2005 Services (to start/stop services). Make sure that the server is running (suggestion: and set to automatic so it starts on reboot)

b) SQL Server Network Configuration. This will show you the protocols that can be used to connect to the instance over the network.. Shared memory, named pipes, TCP/IP, and VIA.. The one you intend to use should be enabled.

c) SQL Native Client Configuration. This will show you the protocols that can be used to connect to the instance using the SQL Native Client. The one you intend to use should be enabled.

4) If that doesn't help, you might need to check your permissions on the server, as well as the DB.. You should be in the windows administrators group to get unfettered access for example..

5) If none of the above helps, uninstall, reboot, and reinstall. It should work right out of the box, eval copy or not..

Hope that helps somebody if not you..

Dan Wood Newbie Points: 9 More actions · Answer 3

At the risk of stating the obvious, keep in mind two things about the evaluation version of SQL 2005. The first is that it is the "Enterprise Evaluation" edition and can only be installed on a Windows Server OS. Setup on Windows XP will run, but it will only let you install the client tools. The other interesting part of the Evaluation edition is that all network protocols are disabled by default. If you want to connect to the server over the network you will have to enable a network protocol with the SQL Server Configuration Utility.

Cheers!

Dan Wood

Minaz Amin SSChampion Points: 11052 More actions · Answer 4

When ever you run a sql installation sql will install or create an instance. There can be only one single default instance and more than one named instances of the SQL. Check if the installtion is successfully completed.

I agree with Dan's points please check that too.

Minaz ...

"More Green More Oxygen !! Plant a tree today"

C Walker Grasshopper Points: 13 More actions · Answer 5

Well it certainly helped me out. I couldn't see the DB instance across the network. Enabling the TCP and Pipes did the trick- so THANK YOU