21

Try running a trace with SQL Profiler while you, and then your coworker, connect to the server. Select RPC, SQL Statement & PreConnect - Starting/Completed. Select Save Results To Table option, then compare the 2 tables to find the bottleneck. Or, since you're connecting by IP, it could be doing a Reverse DNS lookup. If so, add a entry in your hosts ...


19

Microsoft has recently revealed (without a lot of fanfare) that they will be investing in TLS 1.2 and phasing out SSL. It should be relevant to all editions of SQL Server. UPDATE 2016-01-29 : Microsoft has announced official support for TLS 1.2 in 2008, 2008 R2, 2012, & 2014. Downloads and other info can be found in KB #3135244. I blogged about a few ...


18

There are two levels of security that need to be changed in order to allow remote access. SQL Server configuration. By default in Express, Developer, and Enteprise Evaluation editions, connecting by the TCP/IP protocol is disabled. Enable this using SQL Server Configuration Manager. Windows Firewall. While disabling the firewall entirely will work for this ...


16

'Cannot generate SSPI context' is a generic error. It can be caused by many issues, like an outaded password, clock drift, Active Directory access permissions, failure to register an SPN and so on and so forth. There is no solution to this problem. The only 'solution' is to investigate the cause, as per KB811889 and/or Troubleshooting Kerberos Errors. ...


15

I found the answer to my problem in this answer by Remus Rusanu. As an domain-admin connected to that SQL-Server-Host via Remote Desktop. I had to start SQL Server Management Studio explicitly "as an administrator". (right-click -> run as administrator). If SSMS isn't started in administrator mode, the current login is not in "builtin\administrators"-...


15

The least intrusive way to get this working is to either use the following command or have the DBA issue this command for you: use master go GRANT VIEW SERVER STATE TO <user_name>


14

In SSMS, if you run a query in a disconnected window, it will attempt to re-connect to the prior connection. You will get an error, then the window will reconnect. If you run a query like SELECT 1;, it will reconnect without having to do any data access/manipulation. However, I'm a bit timid about relying on this to remember what server I was previously ...


14

SSMS doesn't use ODBC drivers to connect to SQL Server databases. It uses the .Net Framework driver. You cannot choose which driver it uses as it is hard-coded in the application. But why would you need to choose another one? Linked servers are another thing. It is your DB Server itself connecting to another server. If it is SQL Server, it will use its ...


11

Your title says you have an installation problem, but I don't think this is the case (it seems like you have installed SQL Server okay, you just can't find it). Of course I don't know exactly what options you selected during setup, but from the programs applet, it seems like you should have at least one instance installed. The Browse for Servers dialog is ...


10

The problem turned out to be in the connection strings. There are some things you need to consider. First of all there is an option in the publish wizard in Visual Studio in the Settings tab called Use this connection string at runtime (update destination web.config), that for some reason, checked or not, does not seem to work for me. But this may be an ...


10

Taken from the Microsoft Support site: To configure a static port for the specialized Dedicated Administrator Connection (DAC), you must update the registry key that corresponds to your instance. For example, the registry key may be the following: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\MSSQLServer\SuperSocketNetLib\...


9

Go to SQL Server Configuration Manager Start->all program->SQL Server 2008 R2->Configuration Tools->SQL Server Configuration Manager Explore "SQL Server Network Configuration" and then select "Protocols For MSSQLSERVER". Check your TCP/IP Protocols in right side pane. If it is disabled then enabled it and Restart the "Sql Server(MSSQLSERVER) service" ...


9

A PostgreSQL server connection dropping after 10-15 minutes is almost certainly being caused by a state-tracking firewall (possibly using Network Address Translation (NAT)) between the client and the server. Many such firewalls have default timeouts of 15 minutes (900 seconds). The three server-side parameters, tcp_keepalives_idle, tcp_keepalives_interval, ...


9

Just for reference, this problem seems to be related to this Connect bug: Cannot view properties of database when using db owner account - by Jimmy Rudley Posted by Microsoft on 7/9/2013 at 2:47 PM [...] We have corrected this for the next version of SQL 14. Walter A Jokiel, Program Manager, SQL Server I have the same problem with SQL Server 2012 ...


9

Sounds like spotty DNS resolution issues or long running queries. For DNS trouble-shooting As a Band-Aid and trouble-shooting aid add and entry to the hosts file on your app servers (not the SQL Server) at c:\windows\system32\drivers\etc SQLServerIPAddress SQLServerName Example: 172.16.0.5 ProductionSQLBox That way, the SQL Server name will be resolved by ...


8

You selected the default instance name as the name of your instance. Instance Configuration "If you specify MSSQLServer for the instance name, a default instance will be created. For SQL Server Express, if you specify SQLExpress for the instance name, a default instance will be created." To connect to the default instance you don't specify the instance ...


8

On your Windows client, you need to specify the TNS alias @ORCL, or else it assumes you're trying to connect to a local database running on your Windows client, which there isn't one. Also, system as sysdba generally isn't used, not even sure if that makes sense. SYS as sysdba and just plain system are used. Enter user-name: system@ORCL Enter password: ...


8

Connect to SQL Server using Windows authentication. Run sp_readerrorlog and see the complete message which would have come in errorlog when you tried connecting with SQL Authentication. This message is not of much help. You can update the question with message From error log: Login failed for user 'sa'. Reason: An attempt to login using SQL authentication ...


8

This is an extremely common error, with literally millions of search results online. The typical troubleshooting steps include: Make sure the SQL Server service is actually running (SQL Server Configuration Manager > SQL Server Services > check the State of the specific instance and make sure it says "Running", otherwise right-click > Start). Make sure the ...


8

To add to what @RLF provided in his answer; the following will also result in transaction rollback. ALTER DATABASE ... SET SINGLE_USER WITH ROLLBACK IMMEDIATE; will rollback any open transactions. Disconnection by the client, or server, or any bit of infrastructure in between. If the underlying disk subsystem goes away, all open connections to the database ...


8

You need to check your SSL and TLS settings. Check out this KB 3135244. The settings between the client and server should be somewhat consistent (i.e. if the server only allows 1.2 and the client only supports 1.0 I think you might run into issues). Also read through the known issues on that page Updating to a build that supports TLS 1.2 might resolve your ...


8

You can open SSMS as her Windows user account by doing either of the following: Right click the SSMS shortcut while holding the SHIFT key. Click on Open as another user and enter the other users credentials. Create a shortcut in the following format: C:\Windows\System32\runas.exe /savecred /user:DOMAIN\USERNAME "C:\Program Files (x86)\Microsoft SQL ...


8

MSSQL expects OpenSSL v1.0 while Ubuntu 18+ uses OpenSSL 1.1, resulting in a OpenSSL version mismatch. The solution is to symlink ssl v1.0 as below: Stop SQL Server sudo systemctl stop mssql-server Open the editor for the service configuration sudo systemctl edit mssql-server In the editor, add the following lines to the file and save it: [Service] ...


8

The feature designed to help in this scenario is Application Roles. With an Application Role you can allow the user to connect to the target database, but not be able to run any queries until the application supplies a secret to activate the Application Role.


7

To get around this problem, notice that "Windows" is highlighted at the left of the dialog box. I clicked on Database, entered the database credentials, and then it worked.


7

The recommended way to do this is to set up a VPN between the two sites. The steps to do this vary depending on the particular firewall/router being used. If a VPN cannot be used, the following information is provided for how to set up a connection with port mapping. If port-mapping is used, it should only be used in conjunction with additional firewall ...


7

If you are running the GUI on the same machine as the mssql-server service, then you can use localhost for the address (127.0.0.1). If you are running the GUI from a different workstation, you'll need the IPv4 address of the machine where the mssql-server service is running. You can obtain that by running ifconfig from a Linux terminal prompt. Sample ...


7

You would use the Enable-NetFirewallRule cmdlet: Enable-NetFirewallRule -Name "WMI-WINMGMT-In-TCP", "WMI-RPCSS-In-TCP" In order to find the relevant rule names (in order to enable it), you can search existing firewall rules by name by using the Get-NetFirewallRule cmdlet, for example: Get-NetFirewallRule -Name "*WMI*" This uses wildcards to final all the ...


7

LINUX.X64_193000_client.zip is a fully featured installer where you can choose what to install and where, then the installer copies the files to the destination and registers the client. LINUX.X64_193000_client_home.zip is an "image" of and "Administrator" type installation, that you unzip to the destination folder then register it. Simplified Image-Based ...


7

A possible solution is to create a server logon trigger that would check the app_name(). I created the following server trigger on my local instance and tried to connect via ODBC. The connection was rejected. You would have to modify for your needs. CREATE TRIGGER trgGetAppName ON ALL SERVER FOR LOGON AS IF APP_NAME() NOT LIKE ('Microsoft SQL Server ...


Only top voted, non community-wiki answers of a minimum length are eligible