|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
SQL Server Management Studio and Developer EditionI have success managing my Developer edition of SQL Server 2005 when the SS
Management Studio is on the local machine with the SQL Server instance. However, I can't seem to manage another Developer edition on a another machine on my small local network (peer to peer). Is Developer edition of SQL Server 2005 designed not to allow remote administration or do I need to play with security features some more. -- Michael Hockstein Developer edition is local only by default. You will have to enable remote
connections in the Surface Area Configuration tool. If your Dev Edition is not running as the default instance you will also have to enable and start the SQL Browser. -- Show quoteThis posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm "michael" <howlinghound@nospam.nospam> wrote in message news:611CBA53-7419-4507-8E80-EED9A5CFBE08@microsoft.com... >I have success managing my Developer edition of SQL Server 2005 when the SS > Management Studio is on the local machine with the SQL Server instance. > However, I can't seem to manage another Developer edition on a another > machine on my small local network (peer to peer). > > Is Developer edition of SQL Server 2005 designed not to allow remote > administration or do I need to play with security features some more. > > > > > > > -- > Michael Hockstein Whoa! You Da Man!!
So, what is Server Properties/Connections/Remote Server Connections do? Who would have thought that is what the Surface Area Configuration Tool was for. -- Show quoteMichael Hockstein "Roger Wolter[MSFT]" wrote: > Developer edition is local only by default. You will have to enable remote > connections in the Surface Area Configuration tool. If your Dev Edition is > not running as the default instance you will also have to enable and start > the SQL Browser. > > -- > This posting is provided "AS IS" with no warranties, and confers no rights. > Use of included script samples are subject to the terms specified at > http://www.microsoft.com/info/cpyright.htm > > "michael" <howlinghound@nospam.nospam> wrote in message > news:611CBA53-7419-4507-8E80-EED9A5CFBE08@microsoft.com... > >I have success managing my Developer edition of SQL Server 2005 when the SS > > Management Studio is on the local machine with the SQL Server instance. > > However, I can't seem to manage another Developer edition on a another > > machine on my small local network (peer to peer). > > > > Is Developer edition of SQL Server 2005 designed not to allow remote > > administration or do I need to play with security features some more. > > > > > > > > > > > > > > -- > > Michael Hockstein > > > michael (howlinghound@nospam.nospam) writes:
> Whoa! You Da Man!! Nothing you need to know. :-) "Remote server" is a legacy concept from> > So, what is Server Properties/Connections/Remote Server Connections do? the days of SQL 6.5, and is about servers connecting to servers. This concept was already in SQL 7 superseded by linked servers. -- Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx Everything is off by default when you install, even connectivity from
another machine. This is a protection mechanism against hacking, because the majority of SQL Server installs are actually to provide the data store for an application which accesses them locally. The Surface Area Configuration utility has been completely documented and there are thousands of references to it in books, articles, presentations, web seminars, etc. Turning on remote connections is also very well documented as a step in the installation process. -- Show quoteMike http://www.solidqualitylearning.com Disclaimer: This communication is an original work and represents my sole views on the subject. It does not represent the views of any other person or entity either by inference or direct reference. "michael" <howlinghound@nospam.nospam> wrote in message news:8FF7C358-E2A7-41DA-96D1-1C930EBFC871@microsoft.com... > Whoa! You Da Man!! > > So, what is Server Properties/Connections/Remote Server Connections do? > > Who would have thought that is what the Surface Area Configuration Tool > was > for. > > -- > Michael Hockstein > > > "Roger Wolter[MSFT]" wrote: > >> Developer edition is local only by default. You will have to enable >> remote >> connections in the Surface Area Configuration tool. If your Dev Edition >> is >> not running as the default instance you will also have to enable and >> start >> the SQL Browser. >> >> -- >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> Use of included script samples are subject to the terms specified at >> http://www.microsoft.com/info/cpyright.htm >> >> "michael" <howlinghound@nospam.nospam> wrote in message >> news:611CBA53-7419-4507-8E80-EED9A5CFBE08@microsoft.com... >> >I have success managing my Developer edition of SQL Server 2005 when the >> >SS >> > Management Studio is on the local machine with the SQL Server >> > instance. >> > However, I can't seem to manage another Developer edition on a another >> > machine on my small local network (peer to peer). >> > >> > Is Developer edition of SQL Server 2005 designed not to allow remote >> > administration or do I need to play with security features some more. >> > >> > >> > >> > >> > >> > >> > -- >> > Michael Hockstein >> >> >>  |
|||||||||||||||||||||||
Other interesting topics