Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
brendonalexander
Starting Member
3 Posts |
 Posted - 2008-12-02 : 06:19:27
|
| Hi,I hope this is not too much of a stupid question...I have been learning Visual Basic.Net and now I am moving onto SQL Server 2005 in order to start building programs to interact with Databases.I downloaded SQL Server 2005 (180 Evaluation copy) from Microsoft's site, installed it and now whilst following the book "SQL Server 2005 for Dummies" I am trying to setup SQL Server 2005 for the first time.In Microsoft SQL Server Management Studio I have selected the following options:Server Type = Database EngineServer Name = the book is telling me to type "local"Authentication = Windows AuthenticationWhen I click the connect button, I am getting the following message - can anyone advise me as to what I am doing wrong etc?"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)"Any help or guidance would be very much appriciated.Thanks,Bren. |
|
|
darkdusky
Aged Yak Warrior
591 Posts |
Posted - 2008-12-02 : 06:34:36
|
| You need to include the brackets - (local) or alternatively you can use a full stop as shorthand for (local).i.e. Server Name: (local) or . |
 |
|
|
brendonalexander
Starting Member
3 Posts |
Posted - 2008-12-02 : 07:01:00
|
| Thanks for replying darkdusky, but I tried that and it did not work :-(From what I understand from the error message, the SQL Server default settings do not allow remote connections, what ever that means. But how do I change the default settings in SQL Server to allow remore connections.Any ideas? |
|
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2008-12-02 : 07:51:27
|
Have you installed Service Pack2?Are you running on Vista? Please make sure you local user is admin in SQL Server. This happened by default in previous versions of operating systems, but on Vista you have to pay special attention to last step in installation of SQL Server if you want to elevate the current user to administrator in SQL Server.
E 12°55'05.63"N 56°04'39.26" |
|
|
|
brendonalexander
Starting Member
3 Posts |
Posted - 2008-12-02 : 08:42:29
|
| Hi Peso,Thanks for the reply.I belive that I installed SQL Server 2005 and then the Service Pack 2. And yes, I am running Windows Vista Ultimate.I tried running the service pack 2 again and right at the end it comes up with a "SQL Server 2005 User Provisioning Tool for Vista". In this box/tool - it does indeed say that administrative privilages are not assigned automatically. However, in the window it gives you a list box on the left hand side which shows Available Privilages, which you move over to a box on the right hand side to assign privailages to the user. The thing is that, nothing is coming up for me to select - it just remains blank.Do you or anyone else know if this can be done manually somehow?I feel like I am so close, yet so far - it is very frustrating as I just want to get on with my learning :-(Thanks again for your help.Bren. |
|
|
|
|
|
|
|
|
Setting up SQL Server 2005 for first time!