> If you can perform your tasks using SSMSE then it's OK.
>
> However, ensure that you assign least-privilege to the Login and User for
> the remote connection. Otherwise something unexpected can happen (deleting
> some objects by mistake or modifying some data that should not be
> modified... etc.)
>
> --
> Ekrem Önsoy
>
>
>
> "David Clifford" wrote in message
> news:uR2l1IN4IHA.3484@TK2MSFTNGP05.phx.gbl...

>> Hello Ekrem and Andrew.
>>
>> Thank you for this on-going discussion.
>>
>> I have been away all week, but I can report that I did manage to connect
>> to the "remote" version of SQL Server. As usual, it was a case of DOH!!
>> Yes, it was as simple as picking the server from the Connect Server drop
>> box and selecting the server on the network. As I said, I am rather new
>> to SQL Server.
>>
>> Things have changed a little since my last post. I have now set up an
>> Express version on our LOCAL server, and have linked a second Express
>> version to this server via the network, as above for my client.
>>
>> As a new super-speed (?) network link is currently being
>> planned/installed between the office and the quite remote server, we have
>> temporarily abandoned plans to connect to the remote SQL Server until all
>> is up and working. However, this remains an outline of what we want to
>> do:
>>
>> The remote SQL Server is a fully licensed version of SQL Server 2005. I
>> am using the Express version in the office because my client will need to
>> run views and alter tables occasionally. We didn't think that it was
>> really worth the outlay to buy a fully loaded version of SQL Server
>> 2005/8 for these simple few tasks..all other data manipulations/stored
>> procedures etc are done via my VB front-end programme. Back ups to tape
>> would be done remotely. My client is a large organization, and they
>> prefer to keep all SQL Server databases in a secured central SQL Server
>> location in the specialist IT/database department that employs people who
>> are specialists with data storage/security etc. We had discussed having
>> our own licenced copy SQL Server 20052008, but with the cost etc, it was
>> suggested that we use the licenced central server and a copy of Express
>> to just hook up and do a bit of manipulation of our database. As I said,
>> this is now in the future, and we are using an Express SQL Server for the
>> time being.
>>
>> If you do find anything adverse about using Express to link to a licenced
>> SQL Server, please would you let me know via this board?
>>
>> Thank you very much for your time and interest.
>> Regards
>>
>> David
>>
>>
>> "Andrew J. Kelly" shadhawk.com> wrote in message
>> news:OuAlL1i3IHA.4272@TK2MSFTNGP03.phx.gbl...

>>> Well as usual this confuses me even more when it comes to licensing:).
>>> Let me ask around and see what I get from MS directly here but with the
>>> holidays I probably won't get an answer for a while.
>>>
>>> --
>>> Andrew J. Kelly SQL MVP
>>> Solid Quality Mentors
>>>
>>>
>>> "Ekrem Önsoy" compecta.com> wrote in message
>>> news:D071649C-03AE-4AEB-8525-7842EBBDABE5@microsoft.com...

>>>> Recently, there was a question about licensing of the Management Tools
>>>> in "sqlserver.tools" NG. I wondered if we need any type of license to
>>>> use Management Tools on a non-licensed machine so I asked to the Server
>>>> and Tools Product Manager of Microsoft Turkey, whose name is Selma
>>>> Karaca, I had met her on several Microsoft seminars which are held here
>>>> in Istanbul... I'd like to share her reply with you below (I've
>>>> translated it to English now)
>>>>
>>>> By the way, In my question I've mentioned that I'd use the Management
>>>> Tools from a remote machine which is not licensed.
>>>>
>>>> Also, I've told her about the following Q&A in Microsoft' s licensing
>>>> page:
>>>>
>>>> Q & A
>>>> Q. Do I need a separate license to run the SQL Server tools and
>>>> analysis services?
>>>> A. No, a separate license is not required. However, any device that has
>>>> SQL
>>>> Server tools or technologies installed must have a valid SQL Server
>>>> license.
>>>>
>>>> http://www.microsoft.com/sql/howtobuy/faq.mspx
>>>>
>>>> This Q&A seems pretty confusing to me. It says "you don't need a
>>>> separate license" in the first sentence of the answer and then it says
>>>> "you must have a valid SQL Server license to use them"... May be, it's
>>>> mine stupidity.
>>>>
>>>> Anyway, here's the answer of the lady Selam Karaca:
>>>>
>>>> =======================
>>>> Hello Mr. Ekrem,
>>>> You can use the following tools to manage your licensed SQL Server
>>>> instances.
>>>> And you do not need a seperate license to use these tools.
>>>>
>>>> Analysis Services Shared Tools
>>>> Business Intelligence Development Studio
>>>> Connectivity Components
>>>> Legacy Components
>>>> Management Tools
>>>> Notification Services Client Components
>>>> Reporting Services Report Manager
>>>> Reporting Services Shared Tools
>>>> SQL Server 2005 Shared Tools
>>>> Software Development Kit
>>>> SQLXML Client Features
>>>> SQL Server 2005 Books Online
>>>> SQL Server Mobile Server Tools
>>>>
>>>> Hope this helps.
>>>>
>>>> Selma Karaca
>>>> Server and Tools Product Manager | Microsoft Turkey
>>>> Tel: 0212 326 52 31 | Mobile: 0533 683 66 07| skaraca@microsoft.com
>>>>
>>>> =======================
>>>>
>>>> --
>>>> Ekrem Önsoy
>>>>
>>>>
>>>>
>>>> "Andrew J. Kelly" shadhawk.com> wrote in message
>>>> news:%%239RbhzU3IHA.1436@TK2MSFTNGP05.phx.gbl...

>>>>> While I am sure you can connect to a fully licensed instance you need
>>>>> to have a valid CAL for that client regardless of the tool. Even the
>>>>> full version of SSMS requires a valid CAL to use it as well. Since
>>>>> Express does not have a CAL for anything but itself AFAIK I don't
>>>>> think you can legally manage the remote server unless you already have
>>>>> a CAL from another source. I don't know their situation but if they
>>>>> are resorting to Express they most likely don't have it. But as with
>>>>> all licensing questions they should contact a certified vendor or read
>>>>> all the license agreements to be sure.
>>>>>
>>>>> --
>>>>> Andrew J. Kelly SQL MVP
>>>>> Solid Quality Mentors
>>>>>
>>>>>
>>>>> "Ekrem Önsoy" compecta.com> wrote in message
>>>>> news:015D8B4C-DFD6-481E-93BE-0E7765CE45DF@microsoft.com...

>>>>>> Hello Andrew,
>>>>>>
>>>>>> Here's a link from BOL that talks about SSMSE:
>>>>>> http://msdn.microsoft.com/en-us/library/ms365247.aspx
>>>>>>
>>>>>> You can connect to other editions of SQL Server 2005\2000 using SSMSE
>>>>>> and you can manage your databases as long as SSMSE' s limitations
>>>>>> which are listed in the link that I've given above, lets you.
>>>>>>
>>>>>> I have not seen any documentation yet that states connecting other
>>>>>> editions of SQL Server using SSMSE would break any license agreement.
>>>>>> And I don't see any reason for this? SSMSE is a free of charge tool.
>>>>>> As long as the installed should-be-licensed SQL Server instances are
>>>>>> licensed, I don't think it would be a problem to connect to them
>>>>>> using this free tool. Or, did I misunderstand your commet?
>>>>>>
>>>>>> --
>>>>>> Ekrem Önsoy
>>>>>>
>>>>>>
>>>>>>
>>>>>> "Andrew J. Kelly" shadhawk.com> wrote in message
>>>>>> news:%%23U10owS3IHA.2060@TK2MSFTNGP02.phx.gbl...

>>>>>>> AFAIK SQL Server Management Studio Express ONLY supports a SQL
>>>>>>> Express edition database and nothing else. Even if you can connect
>>>>>>> to it and do something I am pretty sure you are voiding the license
>>>>>>> agreement. As Ekrem stated they should have a licensed edition of
>>>>>>> the full client tools (SSMS not Express) and then all they have to
>>>>>>> do is register the server in the registered servers dialog and they
>>>>>>> should be all set.
>>>>>>>
>>>>>>> --
>>>>>>> Andrew J. Kelly SQL MVP
>>>>>>> Solid Quality Mentors
>>>>>>>
>>>>>>>
>>>>>>> "David Clifford" wrote in message
>>>>>>> news:uIYGW1D3IHA.4448@TK2MSFTNGP05.phx.gbl...

>>>>>>>> Thank you Ekrem:
>>>>>>>>

>>>>>>>>>Why not installing only SQL Server Management Studio and connect to
>>>>>>>>>your

>>>>>>>> remote instance and perform actions this way?
>>>>>>>>
>>>>>>>> Yes! that is EXACTLY what I want to do! I have installed SQL Server
>>>>>>>> 2005 Express, and now I want to connect to the remote database and
>>>>>>>> use the Management Studio to manipulate the database. The Alias
>>>>>>>> steps that you highlighted appear to be the answer. But, I am not
>>>>>>>> in the office at the moment to try anything.
>>>>>>>>
>>>>>>>> May I ask..when I have set up my Alias in the SQL Server
>>>>>>>> Configuration Manager, say I call my Alias FOO, what will appear in
>>>>>>>> the Management Studio Object Explorer? And, will I open it up just
>>>>>>>> as I do a regularly listed database?
>>>>>>>>
>>>>>>>> Thank you very much for your time and help here.
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> David
>>>>>>>>
>>>>>>>> "Ekrem Önsoy" compecta.com> wrote in message
>>>>>>>> news:E845E030-14C5-4956-B663-6EDEA5BB0F62@microsoft.com...

>>>>>>>>> First, you can't attach a database in a remote machine in your
>>>>>>>>> network as Andrew has already mantioned.
>>>>>>>>>
>>>>>>>>> Second, you can't attach the sames database more than one instance
>>>>>>>>> of SQL Server at once. One database can be used only by one SQL
>>>>>>>>> Server instance and as far as I understand the database in
>>>>>>>>> question is already attached to a SQL Server instance.
>>>>>>>>>
>>>>>>>>> Why not installing only SQL Server Management Studio and connect
>>>>>>>>> to your remote instance and perform actions this way? Just like
>>>>>>>>> connecting your database in a web hosting company which hosts your
>>>>>>>>> web site and database. Create an Alias in SQL Server Configuration
>>>>>>>>> Manager and use the IP Address (and it's instance name if it's a
>>>>>>>>> Named Instance) of your remote SQL Server instance (The Enterprise
>>>>>>>>> Edition one) and use its port number. Ensure you configure your
>>>>>>>>> firewall locally and on your remote SQL Server server to let you
>>>>>>>>> in and out. Create a Login as User for the database in question
>>>>>>>>> for your user in the office. And he'll be able to connect to your
>>>>>>>>> remote SQL Server instance using only SQL Server Management Studio
>>>>>>>>> to perform actions you desire according to the rights he has been
>>>>>>>>> given.
>>>>>>>>>
>>>>>>>>> So, you don't need to install an instance of SQL Server on the
>>>>>>>>> machine of your user in the office, you only need to tools to
>>>>>>>>> reach to your remote SQL Server instance.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Ekrem Önsoy
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> "David Clifford" wrote in message
>>>>>>>>> news:O%%23wjdvB3IHA.1196@TK2MSFTNGP05.phx.gbl...

>>>>>>>>>> Hello Andrew. Sorry for this confusion. To start again:
>>>>>>>>>>
>>>>>>>>>> We have an SQL Server 2005 Enterprise Edition located in a
>>>>>>>>>> building that is away from our office. "Our" database is
>>>>>>>>>> registered on that server, and the plan is that all
>>>>>>>>>> backups/shrinking etc will be done offsite by the people who
>>>>>>>>>> manage the Enterprise SQL Server 2005 Package. It is preferred
>>>>>>>>>> this way because our organization has a dedicated SQL Server team
>>>>>>>>>> who look after DOZENS of other SQL Server databases that are
>>>>>>>>>> attached to the Enterprose Edition of SQL Server.
>>>>>>>>>>
>>>>>>>>>> My Visual Basic application accesses this remote Enterprise SQL
>>>>>>>>>> Server database via an ODBC link over a LAN. All works well.
>>>>>>>>>>
>>>>>>>>>> But, my client wants to alter tables/write views/stored
>>>>>>>>>> procedures etc., etc. So, instead of leaving his office to go to
>>>>>>>>>> the other building to use the Management console on the
>>>>>>>>>> Enterprise Edition SQL Server 2005, he want to "link" to the
>>>>>>>>>> database on HIS office based computer over the LAN using SQL
>>>>>>>>>> Server 2005 Express and SQL Server Express Management Console.
>>>>>>>>>>
>>>>>>>>>> I installed SQL Server 2005 Express on his machine and tried to
>>>>>>>>>> attach the database that is registered on Enterprise Edition SQL
>>>>>>>>>> Server 2005 using the Express Management console, but all I could
>>>>>>>>>> see in the Drive List box were the two local drives C: and D:,
>>>>>>>>>> and the Master and temp SQL Server databases that were installed
>>>>>>>>>> with the Express SQL Server edition. In the drive list box, the
>>>>>>>>>> network drives were not shown, hence, I could not "see" our
>>>>>>>>>> database on the network in it's folder. I could see them in
>>>>>>>>>> Windows Explorer, but not in the Express Management console.
>>>>>>>>>>
>>>>>>>>>> My question is: Why not? Is it not possible to use the Express
>>>>>>>>>> SQL Server edition attach to our database that is located in the
>>>>>>>>>> other building in order to locally write Views etc? If we can't,
>>>>>>>>>> then we are going to have to trek back and forth to write
>>>>>>>>>> views/stored proceedures etc.
>>>>>>>>>>
>>>>>>>>>> My application work just fine as it connects to the Enterprise
>>>>>>>>>> SQL Server database via an ODBC link, and all is well.
>>>>>>>>>>
>>>>>>>>>> Sorry for this rambling, but the question is, I think, pretty
>>>>>>>>>> fundamental in that we want to be able to control our centrally
>>>>>>>>>> place database in our remote office.
>>>>>>>>>>
>>>>>>>>>> I really hope that this makes sense to you.
>>>>>>>>>>
>>>>>>>>>> In the SQL Server Configuration Manager, I have Enabled TCP/IP.
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>>
>>>>>>>>>> David Clifford
>>>>>>>>>>
>>>>>>>>>> "Andrew J. Kelly" shadhawk.com> wrote in message
>>>>>>>>>> news:uKKv4962IHA.2580@TK2MSFTNGP06.phx.gbl...

>>>>>>>>>>> It's not clear to me what you are asking. You need to separate
>>>>>>>>>>> the two parts here. You have the server which will host the
>>>>>>>>>>> database and the SQL Server Service. The Client can live
>>>>>>>>>>> anywhere as long as it has TCP access to the server. The client
>>>>>>>>>>> can be SQL Server Management Studio, a .net app, a web server
>>>>>>>>>>> etc. it doesn't matter as it is simply talking to the server.
>>>>>>>>>>> You can also have a client on the same machine as the server but
>>>>>>>>>>> that is not a requirement. So if you have a desktop that will be
>>>>>>>>>>> a remote client to a SQL Server on another box that is fine. But
>>>>>>>>>>> it can also be a client to a local copy of SQL Server on that
>>>>>>>>>>> desktop as well. You can use the same client (SSMS) to connect
>>>>>>>>>>> to both and do what you want as long as you have the proper
>>>>>>>>>>> permissions.
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Andrew J. Kelly SQL MVP
>>>>>>>>>>> Solid Quality Mentors
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> "David Clifford" wrote in message
>>>>>>>>>>> news:u%%23lnfg42IHA.4500@TK2MSFTNGP06.phx.gbl...

>>>>>>>>>>>> Thank you for that prompt reply Andrew.
>>>>>>>>>>>>
>>>>>>>>>>>> It is what I suspected.
>>>>>>>>>>>> My main problem then is, if the SQL Database is located at a
>>>>>>>>>>>> remote location..another building for example, then my client
>>>>>>>>>>>> will NOT be able to run queries/change tables/etc using the
>>>>>>>>>>>> Management Consule for a SQL Server 2005 instance on HIS local
>>>>>>>>>>>> machine? Sorry for the rather basic question, but this is all
>>>>>>>>>>>> sort of new to me
>>>>>>>>>>>>
>>>>>>>>>>>> Regards
>>>>>>>>>>>>
>>>>>>>>>>>> David
>>>>>>>>>>>>
>>>>>>>>>>>> "Andrew J. Kelly" shadhawk.com> wrote in
>>>>>>>>>>>> message news:eeWb6H42IHA.2424@TK2MSFTNGP04.phx.gbl...

>>>>>>>>>>>>> That is correct. None of the versions of SQL Server support
>>>>>>>>>>>>> the database files residing on a networked share. But you
>>>>>>>>>>>>> don't attach the db from the server to a client anyway. The
>>>>>>>>>>>>> client should not be the sqls server service itself, it should
>>>>>>>>>>>>> be an application suing the client / server approach. The
>>>>>>>>>>>>> client talks to the server and hence the db thru the SQL
>>>>>>>>>>>>> Server service on the server and thus the client has no need
>>>>>>>>>>>>> to access the files directly.
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Andrew J. Kelly SQL MVP
>>>>>>>>>>>>> Solid Quality Mentors
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> "David Clifford" wrote in message
>>>>>>>>>>>>> news:%%23xkWz432IHA.4988@TK2MSFTNGP06.phx.gbl...

>>>>>>>>>>>>>> Hello All
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> A quick question. We are moving an Access database over to
>>>>>>>>>>>>>> SQL Server 2005. No problems. The SQL Server database will be
>>>>>>>>>>>>>> located on it's own server. To test the system, I installed
>>>>>>>>>>>>>> SQL Server 2005 Express onto the server, got the database
>>>>>>>>>>>>>> attached etc. No problems. I installed the same Express
>>>>>>>>>>>>>> version onto a client computer so that the operator could use
>>>>>>>>>>>>>> the database from his workstation, tried to attach the
>>>>>>>>>>>>>> database, but the network drive was not listed in the file
>>>>>>>>>>>>>> dropdown box..only the local C: and D: drives. My gut says
>>>>>>>>>>>>>> that Express won't look at network drives, anyone care to
>>>>>>>>>>>>>> comment?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thank you
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> David.
>>>>>>>>>>>>>>

>>>>>>>>>>>>>

>>>>>>>>>>>>
>>>>>>>>>>>>

>>>>>>>>>>>

>>>>>>>>>>
>>>>>>>>>>

>>>>>>>>>

>>>>>>>>
>>>>>>>>

>>>>>>>

>>>>>>

>>>>>

>>>>

>>>

>>
>>

>