Re: SQL Server EM/Query Analyzer Access

From: JT (someone_at_microsoft.com)
Date: 05/27/05

  • Next message: Jens Süßmeyer: "Re: login failed for user 'sa'" 
    Date: Fri, 27 May 2005 17:30:21 -0400

    For what it's worth, using SQL Profiler, you can trace the user id and
    application name used when a connection is made, so you can know who is
    connecting via EM or QA.

    "dm4714" <spam@spam.net> wrote in message
    news:eR$Pz7vYFHA.3188@TK2MSFTNGP09.phx.gbl...
    > Hello -- we have SQL Servers running in a Service Bureau environment. How
    > clients frequently use applications at their sites to access our SQL
    Server.
    > Unfortunately, some of our clients are more sophisticated than others and
    > know about Enterprise Manager and Query Analyzer, which they can try and
    use
    > outside of our application... assuming they know a login/password into
    SQL.
    >
    > For those clients that know our SQL Login/Password, and since our
    > application doesn't use application logins, is there a way I can block
    > EM/Query Analyzer access from our clients and keep it available for us
    > internally? Obviously, I cannot block port 1433, but I was hoping I can
    > restrict the apps from being used externally.
    >
    > Thanks
    >
    >

  • Next message: Jens Süßmeyer: "Re: login failed for user 'sa'"

    Relevant Pages

    • Re: Heres a weird one for all of you...
      ... used with that connection string. ... SQL: SQL 2005 Demo ... Additional Major S/W on that server: ... All of my clients timed out ...
      (microsoft.public.sqlserver.connect)
    • Re: Client access to sql database
      ... What ever it is that is attempting to run the report must be making a new ... Andrew J. Kelly SQL MVP ... > that because only 2 of clients have the login issue it must be an xp ... >> to see what the application is using for a connection string. ...
      (microsoft.public.sqlserver.clients)
    • MS SQL 2000 Client connectivity
      ... We have a requirement to test connectivity of clients to ... the SQL 2000 database. ... what I need to accomplish is when the database is running ... to reestablish the connection. ...
      (microsoft.public.sqlserver.connect)
    • Re: Concurrent database access in SQL 2005 Mobile
      ... Please stick to having an "dummy" connection in Open State. ... SQL CE/Mobile has a background thread that flushes the changes ... they run for long hours and we have not seen memory leaks so far. ... then opens his work forms and it's in ...
      (microsoft.public.sqlserver.ce)
    • Re: Concurrent database access in SQL 2005 Mobile
      ... Please stick to having an "dummy" connection in Open State. ... So it is a kind of asynchronous commit which happens every 10 ... I am not sure of this claim as we have many applications built on SQL CE ... then opens his work forms and it's in ...
      (microsoft.public.sqlserver.ce)