Can't connect to local server

[alsaffar]

Hi Helpers ('',)

I'm newbie to MS SQL Server 2005, I just installed it

I want to start creating the database on my local pc

I searched alot for newbies tutorial with picture but I couldn't find! All they assumed I'm connected to a server

The problem is I can't connect to my local server!

How can I connect to my local pc to start creating my DB?

 

[Catadmin]

Did you install the actual server or just the client tools?

If you installed the Developer version, you can just type localhost in the Servername and then use the login name and password you set up for the SA account or one of the SQL Services account. If you used local admin account, just use that.

Or you can type in your actual computer name as the Servername. Both assume you set up a default instance instead of a named instance.

BTW, we've had to use the port # to get connected here, otherwise SQL 2k5 might time out searching for a port. Assuming you kept all the defaults (including port default), try "Localhost, 1433".

Also, check your SQL Server Surface COnfiguration Tool to make sure you've enabled network protocols (otherwise you'll never be able to connect).



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[alsaffar]

Thanks Catadmin for your reply ('',)

I have the Enterprise Edition and I couldn't find where to setup the server! Please be patient since I'm totally new to SQL Server

The following are the 2 setup options I have:

http://img87.imageshack.us/img87/5539/cd1vv1.jpg

http://img180.imageshack.us/img180/8357/cd2xo4.jpg

Please help

 

[onpnt]

You shouldn't install enterprise on you local machine for one. Is there some reason why you did or tried to? Is that the edition you came to after analyzing the needs of you environment?

If you want to simply learn SQL Server in all I would get yourself a copy of developer edition and install that or if the requirements meet SQLExpress that is a good learning model. If you want to start designing a database to meet some application requirements diving rate into creating it is not the way to go. There are steps you should not skip in the designing model.

you can start here

Installing a db server can be as simple as next, next...finish but you should really know the best and proper way to do you the installation to meet your requirements. I would highly suggest getting some reading materials to help you get going on what setup you want. If you go the right route in getting the right knowledge then the actual installation will be a null point and straight forward (in most cases )

[sub]____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done[/sub]

 

[Catadmin]

As onpnt said, you can't install the server from Enterprise on your desktop. You'll need to use Developer, or you can download Express from this link:

http://www.microsoft.com/sql/editions/express/default.mspx

Be warned, Express is a very limited tool. But it should be enough to get you started with training. Also, at this link you can download a 180 day trial of Enterprise:

http://www.microsoft.com/sql/editions/enterprise/default.mspx

Here is a page with all the requirements, including operating system versions, of all SQL 25k editions.

http://www.microsoft.com/sql/editions/enterprise/sysreqs.mspx

Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[SQLBill]

Remember, as the others have kind of stated, - Standard and Enterprise editions are for servers, not workstations. Those editions will ONLY install the client tools on workstations. So unless your local machine is a server, you need to follow their advice and get the Developer or Express version.

-SQLBill

Posting advice: FAQ481-4875

 

[alsaffar]

Hi everybody, I apreciate evry single word you said ('',)

One thing I didn't understood; why Enterprise edition isn't the right edition for me while its shown in the comparison page its including all other editions!

http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

 

[onpnt]

If I understand what you meant by that you seemed to have just picked the one that has the most features. Enterprise does of course but picking the correct version for your environment cannot be done based on the full featured package. You should fully analyze what each edition offers and compare licensing and cost along with that. I'm guessing sense you attempted to install enterprise on your machine the analyze could go a bit deeper.

I guess unless your company has that much money to blow. Or you have a subscription from M$ and get the discs along with installing them on anything you like ignoring the details of that agreement ;-)


[sub]____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done[/sub]

 

[alsaffar]

Thanks onpnt for your quick reply

I work in a bank, and the only edition they bought was "Enterprise Edition", because of this I installed it without looking at the other editions sine Enterprise got them all

Regardless that "Enterprise" is beyond what I need, do I need to install another edition like "Developer"?

All what I want now is to connect to a local server to start design my database.

Note that I'm new to MS SQL Server but I spend more than 6 years with Oracle DB

 

[alsaffar]

I forgot to say, my OS is Windows XP Professional SP2

 

[onpnt]

Yes to Developer

Enterprise does not have the other editions. It has the features of the other editions but does not actually let you select other editions. Unless I completely didn't understand what you meant by "sine Enterprise got them all"

[sub]____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done[/sub]

 

[alsaffar]

Dear onpnt,

I didn't mean "when installing Eterprise; it'll ask me which edition I want to install", NO, I meant that "Enterprise edition got all the featuers that other editions got"

Now my question is, with "Etnerprise edition" that I have already installed; is there's a way to connect to local server? Because currently I can't login to "localhost" it give me the following error:

TITLE: Connect to Server
Cannot connect to localhost.

ADDITIONAL INFORMATION:
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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

 

[onpnt]

Alright, I guess I'll say it one more time sense I have seen no inclination otherwise from the original specifications you've listed.

32-bit OS Minimum Allowances for Enterprise Edition

Microsoft Windows 2000 Server with Service Pack (SP) 4 or later; Windows Server 2003 Standard Edition, Enterprise Edition, or Datacenter Edition with SP 1 or later; Windows Small Business Server 2003 with SP 1 or later

You have not installed SQL Server 2005 Enterprise Edition on Windows XP but more likely (again) have installed the client tools.

I think there really isn't much more to say on this subject

[sub]____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done[/sub]

 

[Catadmin]

Enterprise edition may be the "right one", but it will NOT work on a PC operating system. That's why you need Developer edition (which is Enterprise edition licensed only for development purposes and cannot be put in production).

If you can't get Developer edition, install Enterprise on a SERVER, then have your client tools connect to that server. You will NOT be connecting to a local server.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[SQLBill]

Here's the big question....WHERE did you run the installation of Enterprise Edition?

1. On the Server.
2. On your workstation

If you ran it ON the server, then it should have installed everything.

If you ran it ON your workstation, then it did NOT get installed.

You MUST run the software on the system where it is going to be used. So running it on your workstation does not install it on a server.

-SQLBill

Posting advice: FAQ481-4875

 

[alsaffar]

Thanks onpnt, finally I got an easy answer ('',)

I got my goal after installing Windows Server 2003 instead of Windows XP Professional, and then I installed SQL Server 2005 Enterprise without any problem.

Catadmin, do you mean by "You will NOT be connecting to a local server"? Because I managed to connect to the server from the same server itself!!

SQLBill, thanks for input

 

[Catadmin]

I meant if you were installing the client tools on a desktop machine like XP and then installed the server on an actual server, then you would not be connecting to a local instance because you would be crossing the network. I didn't actually think you would be running the client tools from the server itself (which isn't the best idea in the world, but as long as it's only a dev/sandbox server, you should be okay).

You say you installed WIndows 2003 on your machine. Are you saying you installed it on your desktop? If so, be very very careful. This is a huge security risk just for the sake of development. Not only can the Server OS do a lot more (and therefore is a lot more vunerable to viruses and hack attacks) than a PC OS, but generally PCs don't have the hardware to properly run a Server OS.

If I were you, I'd take the machine off the network entirely so you can do your development without worrying about all the network noise your PC will now generate and the virus issues.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[alsaffar]

First of all, thank you very much Catadmin for your detailed reply, I really apreciate it

If I were you, I'd take the machine off the network entirely so you can do your development without worrying about all the network noise your PC will now generate and the virus issues

My PC which is Windows 2003 Server OS is connected to the internet and I jave Norton Antivirus Server 10 installed plus the Firewall which came with SP1, do I have still worry about "Internet Threats" more than any normal PC with Windows XP OS ??

 

[Catadmin]

Short answer? Yes.

I used to do network/desktop support before I became a DBA, which is why I emphasize this so strongly. So, please don't take this as a flame, because it's not intended that way.

Just because you have all that stuff doesn't mean your machine isn't vunerable. Windows 2003 Server has a lot of stuff turned off by default but it's still got a lot of issues. Subscribe to the Microsoft Security Alert bulletins if you don't believe me. @=) And because it is a Server OS, its nature dictates that it can reach out to other computers and do "bad stuff". If you get an email on your PC that has a trojan designed to turn your box into a zombie, then you get to explain to the rest of IT why you installed a server OS on a PC.

If you're going to leave your PC attached to the network, you're going to have to practice all kinds of restraint in visiting web pages and opening emails. Restraint you may never had needed to worry about before. Cookies can track your information and a Server OS can "sense" other servers on the network. If someone managed to hijack your IE browser and put a sniffer or keystroke logger on it, then it could compromise your entire network.

Yes, I'm paranoid. Maybe a little more than the average user. But I've seen too many other people go down this path and lose their jobs over the resulting chaos. Therefore, I don't recommend this to anyone.

If you're not going to remove your machine from the network, you should at least contact your network / server / security team (if you have one) to make sure your box is locked down tight. Also, you'll probably want to do internet browsing and email on another machine so you don't tempt fate. Lastly, you'll need to be very careful about using USB drives / floppies / CDs & DVDs to install files, music or pictures that you got from home or friends.

Anyway, I hope my advice helps you out. And remember, just because I'm paranoid doesn't mean the hackers *aren't* out to get me. @=)



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"