Home > Articles > Data > SQL Server

📄 Contents

  1. SQL Server Reference Guide
  2. Introduction
  3. SQL Server Reference Guide Overview
  4. Table of Contents
  5. Microsoft SQL Server Defined
  6. SQL Server Editions
  7. SQL Server Access
  8. Informit Articles and Sample Chapters
  9. Online Resources
  10. Microsoft SQL Server Features
  11. SQL Server Books Online
  12. Clustering Services
  13. Data Transformation Services (DTS) Overview
  14. Replication Services
  15. Database Mirroring
  16. Natural Language Processing (NLP)
  17. Analysis Services
  18. Microsot SQL Server Reporting Services
  19. XML Overview
  20. Notification Services for the DBA
  21. Full-Text Search
  22. SQL Server 2005 - Service Broker
  23. Using SQL Server as a Web Service
  24. SQL Server Encryption Options Overview
  25. SQL Server 2008 Overview
  26. SQL Server 2008 R2 Overview
  27. SQL Azure
  28. The Utility Control Point and Data Application Component, Part 1
  29. The Utility Control Point and Data Application Component, Part 2
  30. Microsoft SQL Server Administration
  31. The DBA Survival Guide: The 10 Minute SQL Server Overview
  32. Preparing (or Tuning) a Windows System for SQL Server, Part 1
  33. Preparing (or Tuning) a Windows System for SQL Server, Part 2
  34. Installing SQL Server
  35. Upgrading SQL Server
  36. SQL Server 2000 Management Tools
  37. SQL Server 2005 Management Tools
  38. SQL Server 2008 Management Tools
  39. SQL Azure Tools
  40. Automating Tasks with SQL Server Agent
  41. Run Operating System Commands in SQL Agent using PowerShell
  42. Automating Tasks Without SQL Server Agent
  43. Storage – SQL Server I/O
  44. Service Packs, Hotfixes and Cumulative Upgrades
  45. Tracking SQL Server Information with Error and Event Logs
  46. Change Management
  47. SQL Server Metadata, Part One
  48. SQL Server Meta-Data, Part Two
  49. Monitoring - SQL Server 2005 Dynamic Views and Functions
  50. Monitoring - Performance Monitor
  51. Unattended Performance Monitoring for SQL Server
  52. Monitoring - User-Defined Performance Counters
  53. Monitoring: SQL Server Activity Monitor
  54. SQL Server Instances
  55. DBCC Commands
  56. SQL Server and Mail
  57. Database Maintenance Checklist
  58. The Maintenance Wizard: SQL Server 2000 and Earlier
  59. The Maintenance Wizard: SQL Server 2005 (SP2) and Later
  60. The Web Assistant Wizard
  61. Creating Web Pages from SQL Server
  62. SQL Server Security
  63. Securing the SQL Server Platform, Part 1
  64. Securing the SQL Server Platform, Part 2
  65. SQL Server Security: Users and other Principals
  66. SQL Server Security – Roles
  67. SQL Server Security: Objects (Securables)
  68. Security: Using the Command Line
  69. SQL Server Security - Encrypting Connections
  70. SQL Server Security: Encrypting Data
  71. SQL Server Security Audit
  72. High Availability - SQL Server Clustering
  73. SQL Server Configuration, Part 1
  74. SQL Server Configuration, Part 2
  75. Database Configuration Options
  76. 32- vs 64-bit Computing for SQL Server
  77. SQL Server and Memory
  78. Performance Tuning: Introduction to Indexes
  79. Statistical Indexes
  80. Backup and Recovery
  81. Backup and Recovery Examples, Part One
  82. Backup and Recovery Examples, Part Two: Transferring Databases to Another System (Even Without Backups)
  83. SQL Profiler - Reverse Engineering An Application
  84. SQL Trace
  85. SQL Server Alerts
  86. Files and Filegroups
  87. Partitioning
  88. Full-Text Indexes
  89. Read-Only Data
  90. SQL Server Locks
  91. Monitoring Locking and Deadlocking
  92. Controlling Locks in SQL Server
  93. SQL Server Policy-Based Management, Part One
  94. SQL Server Policy-Based Management, Part Two
  95. SQL Server Policy-Based Management, Part Three
  96. Microsoft SQL Server Programming
  97. An Outline for Development
  98. Database
  99. Database Services
  100. Database Objects: Databases
  101. Database Objects: Tables
  102. Database Objects: Table Relationships
  103. Database Objects: Keys
  104. Database Objects: Constraints
  105. Database Objects: Data Types
  106. Database Objects: Views
  107. Database Objects: Stored Procedures
  108. Database Objects: Indexes
  109. Database Objects: User Defined Functions
  110. Database Objects: Triggers
  111. Database Design: Requirements, Entities, and Attributes
  112. Business Process Model Notation (BPMN) and the Data Professional
  113. Business Questions for Database Design, Part One
  114. Business Questions for Database Design, Part Two
  115. Database Design: Finalizing Requirements and Defining Relationships
  116. Database Design: Creating an Entity Relationship Diagram
  117. Database Design: The Logical ERD
  118. Database Design: Adjusting The Model
  119. Database Design: Normalizing the Model
  120. Creating The Physical Model
  121. Database Design: Changing Attributes to Columns
  122. Database Design: Creating The Physical Database
  123. Database Design Example: Curriculum Vitae
  124. NULLs
  125. The SQL Server Sample Databases
  126. The SQL Server Sample Databases: pubs
  127. The SQL Server Sample Databases: NorthWind
  128. The SQL Server Sample Databases: AdventureWorks
  129. The SQL Server Sample Databases: Adventureworks Derivatives
  130. UniversalDB: The Demo and Testing Database, Part 1
  131. UniversalDB: The Demo and Testing Database, Part 2
  132. UniversalDB: The Demo and Testing Database, Part 3
  133. UniversalDB: The Demo and Testing Database, Part 4
  134. Getting Started with Transact-SQL
  135. Transact-SQL: Data Definition Language (DDL) Basics
  136. Transact-SQL: Limiting Results
  137. Transact-SQL: More Operators
  138. Transact-SQL: Ordering and Aggregating Data
  139. Transact-SQL: Subqueries
  140. Transact-SQL: Joins
  141. Transact-SQL: Complex Joins - Building a View with Multiple JOINs
  142. Transact-SQL: Inserts, Updates, and Deletes
  143. An Introduction to the CLR in SQL Server 2005
  144. Design Elements Part 1: Programming Flow Overview, Code Format and Commenting your Code
  145. Design Elements Part 2: Controlling SQL's Scope
  146. Design Elements Part 3: Error Handling
  147. Design Elements Part 4: Variables
  148. Design Elements Part 5: Where Does The Code Live?
  149. Design Elements Part 6: Math Operators and Functions
  150. Design Elements Part 7: Statistical Functions
  151. Design Elements Part 8: Summarization Statistical Algorithms
  152. Design Elements Part 9:Representing Data with Statistical Algorithms
  153. Design Elements Part 10: Interpreting the Data—Regression
  154. Design Elements Part 11: String Manipulation
  155. Design Elements Part 12: Loops
  156. Design Elements Part 13: Recursion
  157. Design Elements Part 14: Arrays
  158. Design Elements Part 15: Event-Driven Programming Vs. Scheduled Processes
  159. Design Elements Part 16: Event-Driven Programming
  160. Design Elements Part 17: Program Flow
  161. Forming Queries Part 1: Design
  162. Forming Queries Part 2: Query Basics
  163. Forming Queries Part 3: Query Optimization
  164. Forming Queries Part 4: SET Options
  165. Forming Queries Part 5: Table Optimization Hints
  166. Using SQL Server Templates
  167. Transact-SQL Unit Testing
  168. Index Tuning Wizard
  169. Unicode and SQL Server
  170. SQL Server Development Tools
  171. The SQL Server Transact-SQL Debugger
  172. The Transact-SQL Debugger, Part 2
  173. Basic Troubleshooting for Transact-SQL Code
  174. An Introduction to Spatial Data in SQL Server 2008
  175. Performance Tuning
  176. Performance Tuning SQL Server: Tools and Processes
  177. Performance Tuning SQL Server: Tools Overview
  178. Creating a Performance Tuning Audit - Defining Components
  179. Creating a Performance Tuning Audit - Evaluation Part One
  180. Creating a Performance Tuning Audit - Evaluation Part Two
  181. Creating a Performance Tuning Audit - Interpretation
  182. Creating a Performance Tuning Audit - Developing an Action Plan
  183. Understanding SQL Server Query Plans
  184. Performance Tuning: Implementing Indexes
  185. Performance Monitoring Tools: Windows 2008 (and Higher) Server Utilities, Part 1
  186. Performance Monitoring Tools: Windows 2008 (and Higher) Server Utilities, Part 2
  187. Performance Monitoring Tools: Windows System Monitor
  188. Performance Monitoring Tools: Logging with System Monitor
  189. Performance Monitoring Tools: User Defined Counters
  190. General Transact-SQL (T-SQL) Performance Tuning, Part 1
  191. General Transact-SQL (T-SQL) Performance Tuning, Part 2
  192. General Transact-SQL (T-SQL) Performance Tuning, Part 3
  193. Performance Monitoring Tools: An Introduction to SQL Profiler
  194. Performance Tuning: Introduction to Indexes
  195. Performance Monitoring Tools: SQL Server 2000 Index Tuning Wizard
  196. Performance Monitoring Tools: SQL Server 2005 Database Tuning Advisor
  197. Performance Monitoring Tools: SQL Server Management Studio Reports
  198. Performance Monitoring Tools: SQL Server 2008 Activity Monitor
  199. The SQL Server 2008 Management Data Warehouse and Data Collector
  200. Performance Monitoring Tools: Evaluating Wait States with PowerShell and Excel
  201. Practical Applications
  202. Choosing the Back End
  203. The DBA's Toolbox, Part 1
  204. The DBA's Toolbox, Part 2
  205. Scripting Solutions for SQL Server
  206. Building a SQL Server Lab
  207. Using Graphics Files with SQL Server
  208. Enterprise Resource Planning
  209. Customer Relationship Management (CRM)
  210. Building a Reporting Data Server
  211. Building a Database Documenter, Part 1
  212. Building a Database Documenter, Part 2
  213. Data Management Objects
  214. Data Management Objects: The Server Object
  215. Data Management Objects: Server Object Methods
  216. Data Management Objects: Collections and the Database Object
  217. Data Management Objects: Database Information
  218. Data Management Objects: Database Control
  219. Data Management Objects: Database Maintenance
  220. Data Management Objects: Logging the Process
  221. Data Management Objects: Running SQL Statements
  222. Data Management Objects: Multiple Row Returns
  223. Data Management Objects: Other Database Objects
  224. Data Management Objects: Security
  225. Data Management Objects: Scripting
  226. Powershell and SQL Server - Overview
  227. PowerShell and SQL Server - Objects and Providers
  228. Powershell and SQL Server - A Script Framework
  229. Powershell and SQL Server - Logging the Process
  230. Powershell and SQL Server - Reading a Control File
  231. Powershell and SQL Server - SQL Server Access
  232. Powershell and SQL Server - Web Pages from a SQL Query
  233. Powershell and SQL Server - Scrubbing the Event Logs
  234. SQL Server 2008 PowerShell Provider
  235. SQL Server I/O: Importing and Exporting Data
  236. SQL Server I/O: XML in Database Terms
  237. SQL Server I/O: Creating XML Output
  238. SQL Server I/O: Reading XML Documents
  239. SQL Server I/O: Using XML Control Mechanisms
  240. SQL Server I/O: Creating Hierarchies
  241. SQL Server I/O: Using HTTP with SQL Server XML
  242. SQL Server I/O: Using HTTP with SQL Server XML Templates
  243. SQL Server I/O: Remote Queries
  244. SQL Server I/O: Working with Text Files
  245. Using Microsoft SQL Server on Handheld Devices
  246. Front-Ends 101: Microsoft Access
  247. Comparing Two SQL Server Databases
  248. English Query - Part 1
  249. English Query - Part 2
  250. English Query - Part 3
  251. English Query - Part 4
  252. English Query - Part 5
  253. RSS Feeds from SQL Server
  254. Using SQL Server Agent to Monitor Backups
  255. Reporting Services - Creating a Maintenance Report
  256. SQL Server Chargeback Strategies, Part 1
  257. SQL Server Chargeback Strategies, Part 2
  258. SQL Server Replication Example
  259. Creating a Master Agent and Alert Server
  260. The SQL Server Central Management System: Definition
  261. The SQL Server Central Management System: Base Tables
  262. The SQL Server Central Management System: Execution of Server Information (Part 1)
  263. The SQL Server Central Management System: Execution of Server Information (Part 2)
  264. The SQL Server Central Management System: Collecting Performance Metrics
  265. The SQL Server Central Management System: Centralizing Agent Jobs, Events and Scripts
  266. The SQL Server Central Management System: Reporting the Data and Project Summary
  267. Time Tracking for SQL Server Operations
  268. Migrating Departmental Data Stores to SQL Server
  269. Migrating Departmental Data Stores to SQL Server: Model the System
  270. Migrating Departmental Data Stores to SQL Server: Model the System, Continued
  271. Migrating Departmental Data Stores to SQL Server: Decide on the Destination
  272. Migrating Departmental Data Stores to SQL Server: Design the ETL
  273. Migrating Departmental Data Stores to SQL Server: Design the ETL, Continued
  274. Migrating Departmental Data Stores to SQL Server: Attach the Front End, Test, and Monitor
  275. Tracking SQL Server Timed Events, Part 1
  276. Tracking SQL Server Timed Events, Part 2
  277. Patterns and Practices for the Data Professional
  278. Managing Vendor Databases
  279. Consolidation Options
  280. Connecting to a SQL Azure Database from Microsoft Access
  281. SharePoint 2007 and SQL Server, Part One
  282. SharePoint 2007 and SQL Server, Part Two
  283. SharePoint 2007 and SQL Server, Part Three
  284. Querying Multiple Data Sources from a Single Location (Distributed Queries)
  285. Importing and Exporting Data for SQL Azure
  286. Working on Distributed Teams
  287. Professional Development
  288. Becoming a DBA
  289. Certification
  290. DBA Levels
  291. Becoming a Data Professional
  292. SQL Server Professional Development Plan, Part 1
  293. SQL Server Professional Development Plan, Part 2
  294. SQL Server Professional Development Plan, Part 3
  295. Evaluating Technical Options
  296. System Sizing
  297. Creating a Disaster Recovery Plan
  298. Anatomy of a Disaster (Response Plan)
  299. Database Troubleshooting
  300. Conducting an Effective Code Review
  301. Developing an Exit Strategy
  302. Data Retention Strategy
  303. Keeping Your DBA/Developer Job in Troubled Times
  304. The SQL Server Runbook
  305. Creating and Maintaining a SQL Server Configuration History, Part 1
  306. Creating and Maintaining a SQL Server Configuration History, Part 2
  307. Creating an Application Profile, Part 1
  308. Creating an Application Profile, Part 2
  309. How to Attend a Technical Conference
  310. Tips for Maximizing Your IT Budget This Year
  311. The Importance of Blue-Sky Planning
  312. Application Architecture Assessments
  313. Transact-SQL Code Reviews, Part One
  314. Transact-SQL Code Reviews, Part Two
  315. Cloud Computing (Distributed Computing) Paradigms
  316. NoSQL for the SQL Server Professional, Part One
  317. NoSQL for the SQL Server Professional, Part Two
  318. Object-Role Modeling (ORM) for the Database Professional
  319. Business Intelligence
  320. BI Explained
  321. Developing a Data Dictionary
  322. BI Security
  323. Gathering BI Requirements
  324. Source System Extracts and Transforms
  325. ETL Mechanisms
  326. Business Intelligence Landscapes
  327. Business Intelligence Layouts and the Build or Buy Decision
  328. A Single Version of the Truth
  329. The Operational Data Store (ODS)
  330. Data Marts – Combining and Transforming Data
  331. Designing Data Elements
  332. The Enterprise Data Warehouse — Aggregations and the Star Schema
  333. On-Line Analytical Processing (OLAP)
  334. Data Mining
  335. Key Performance Indicators
  336. BI Presentation - Client Tools
  337. BI Presentation - Portals
  338. Implementing ETL - Introduction to SQL Server 2005 Integration Services
  339. Building a Business Intelligence Solution, Part 1
  340. Building a Business Intelligence Solution, Part 2
  341. Building a Business Intelligence Solution, Part 3
  342. Tips and Troubleshooting
  343. SQL Server and Microsoft Excel Integration
  344. Tips for the SQL Server Tools: SQL Server 2000
  345. Tips for the SQL Server Tools – SQL Server 2005
  346. Transaction Log Troubles
  347. SQL Server Connection Problems
  348. Orphaned Database Users
  349. Additional Resources
  350. Tools and Downloads
  351. Utilities (Free)
  352. Tool Review (Free): DBDesignerFork
  353. Aqua Data Studio
  354. Microsoft SQL Server Best Practices Analyzer
  355. Utilities (Cost)
  356. Quest Software's TOAD for SQL Server
  357. Quest Software's Spotlight on SQL Server
  358. SQL Server on Microsoft's Virtual PC
  359. Red Gate SQL Bundle
  360. Microsoft's Visio for Database Folks
  361. Quest Capacity Manager
  362. SQL Server Help
  363. Visual Studio Team Edition for Database Professionals
  364. Microsoft Assessment and Planning Solution Accelerator
  365. Aggregating Server Data from the MAPS Tool

Many programs don't have any connections that you have to configure. For instance, when you work with a document in Microsoft Word, the program handles all the connections to the hard drive subsystem and identifies everything it needs to open and work with the document.

In larger, more open platforms like an application against a database, it isn't quite as simple. The data isn't in a single, constant location, but instead most often is on a server across a network connection. In fact, there are multiple issues to consider, not just where the data is located. Database applications have layers of security as well, and not just at the database level.

In this overview I'll deal with some of the more common issues that you might encounter when you try to connect to SQL Server, and I'll cover some steps you can follow to find and fix them. I'll explain some of the issues you'll have in SQL Server 2000, and SQL Server 2005 and higher. I'll focus a little more on 2005 and higher, since that’s what most organizations are now using. The newer versions of SQL Server have more secure infrastructures, so you'll sometimes encounter more issues with those.

Basic Troubleshooting

To begin any troubleshooting exercise, you first need to isolate the problem to the proper component. That means identifying all the components in the environment and then ensuring that each one is functioning properly. When you find the component that isn't working, you simply correct it and see if you're able to connect. Sometimes you’ll have more than one problem, so you need to fix them one at a time to get to the next one.

That's often easier said than done, however. Sometimes there are so many variables involved with even one component that solving for each one would take a lot of time, which you don't have in an emergency. In other cases the variables change so quickly there isn't a stable state you can observe.

The place to start is to ask these two questions:

  1. Was it working before?
  2. What Changed?

The answer is normally “yes” to the first one and “nothing” to the second, which of course can’t be true. If it was working and now isn’t, then you need to find what changed. Perhaps it’s true that no one changed anything manually, but certainly something changed or broke to bring you to this state.

If it’s a change that someone initiated (changing a setting, stopping a service, rebooting a router) then make it easy for them to tell you. Sometimes people are afraid that they will get into trouble if they get “found out,” so they stay quiet. Meanwhile, you spend hours locating what they did. If you let them “off the hook” by not “pressing charges,” then maybe you’ll get the answer faster, which is what you’re after anyway.

On the other hand, perhaps no one really did make a manual change. That means that a state change occurred because of another system activity, or because something physically broke. The trick is locating that change. The fix for this problem is to eliminate as many variables as possible.

Of course, the first thing to check is all the logs. You should first open and examine the Windows Event logs. You should also check the SQL Server Error Logs, which are just text files. They are located in the SQL Server directory under Program Files, in a subdirectory called LOGS. Those two sets of logs will tell you at least the system state before things went wrong. After that, you need to do a little more investigating. Here are a few tips that will help you do that.

Find out how many applications are affected

Is this issue happening to everyone in all applications, or just a few? If the server is not responding to anyone, make sure you check the services on the SQL Server system to see if they are running. You can do that with the NET START command at a CMD prompt, or you can use the Services applet in the Windows Control Panel. Remember, any changes to the Services for SQL Server 2005 and higher should be done in SQL Server’s Configuration Manager tool, but checking, starting or stopping a service is OK to do from the Control Panel in Windows.

But don’t just start the services — check to see why they are not running. First, ask anyone you suspect that might have stopped them (other DBA’s, developers, system administrators, etc.) and then check the Windows Event logs. You can also check the SQL Server Error Logs. The reason you’re checking is in case there is a physical issue with the database or log files. If so, you want to stop what you’re doing and take a full system backup with the services down. That way, no matter what, you can’t make the situation any worse than it is. If you try and start the services blindly, SQL Server might actually try and recover the files on a damaged file system and destroy the files forever.

Once you’ve taken that backup, you can move on to more intense recovery processes, which I won’t cover here. If you’re not an Expert DBA at this point, it’s best to call Microsoft Support for help. Detail what the situation is, and explain what you’ve done up until this point.

If the server is responding to only one request, it might be that the Instance or database is set to single user mode. Open Enterprise Manager (SQL Server 2000 and lower) or Management Studio (SQL Server 2005 and higher) and right-click the Instance name and select Properties. You'll see there if the Instance is in single user mode. If you’re using SQL Server 2005 and higher, the administrator can still connect to the Instance even when it is in single user mode, using the Dedicated Admin Connection, or DAC. More on that is here.

Don't just change the mode back to multi-user — find out why it was set that way. There might have been a process that changed the state or perhaps another administrator changed it. This will be recorded in the SQL Server logs or in the Application Log of the Event Viewer in Windows. Once you've found the reason and corrected it, you can change the state of the database or Instance back to allow the users in.

If more than one group of users are able to access the database but others are not, find out what the differences between them are. Perhaps they are using a different network protocol or connection method. That may point you to the problem area.

If some groups of users are not able to get in but others are and the application, network and other settings are the same, you may be facing a permissions issue.

Try to connect directly on the server

One of the quickest ways to determine a networking or connection problem is to try and connect to the database directly on the server. Open a command prompt on the server, and type the following statement. This works on SQL Server 2000 and lower versions:

osql –e –d master

And this one works on SQL Server 2005 and higher:

sqlcmd –E –d master 

Note that if you’re using a named Instance, you’ll have to add the name of the server like this (my system is named Buck and my Instance is named SQL2K8)

sqlcmd –S Buck\SQL2K8 –E –d master 

Those commands will drop you in the SQLCMD command line, and you can type this:

SELECT @@VERSION
GO
QUIT

If this works, the server is responding. If it doesn't, then probably no one is getting in and you need to check the services for SQL Server to see if they are started. Once again, don't start them until you have checked all the logs to ensure you know why they stopped.

If that statement does work, replace the word "master" with the name of the application's database. Then type in a simple query that should work with your application. If those work, then you're back to an issue from the network connection out. From there try running the same query on a system that has SQL Server client tools installed, and you can rule out the network connection itself, and then investigate one connection from the application. If the second statement doesn't work, you need to investigate the database state. I’ll explain that in a moment.

Check Connections

I’ll actually mention this element throughout this article, since it can surface in a lot of different components, but once you’ve verified you can connect to the database on the server, then you need to find out why others can’t. The next logical step is to check the network settings.

The first thing to do is to see if the Windows server running the SQL Server Instance can connect to your network. You can use the ping command with the name or IP address of another system, or simply open a known network share on another system from the server. Make sure that you have the proper security taken into account — you don’t want to believe it’s a network issue when you just don’t have permission to the share.

Assuming that you can ping or connect out from the server, the next step is to see if you can ping in to the server from a client, or open a share on the Windows Server running SQL Server from another system.

If all of that works, then you might be facing a firewall issue. These are really not that hard to investigate, but the fix might be more difficult. Since you might be using one of any dozens of firewalls, I can’t advise you on the steps to troubleshoot that, but your vendor can. Books Online has a great article on firewalls and SQL Server settings that you can read here.

If you’re still not able to connect due to a network issue, it’s time to involve your networking professionals.

Use Graphical tools to investigate the server and database

Once you’ve used the command-line tools to investigate the system and ensure that at least the server is running, you can move on to a more in-depth investigation. When you’re in a hurry and things aren’t going well, it’s nice to use the graphical tools so that you can gather a lot of information quickly.

Start with the database state — you’re working from the “back end” forward to the application this way.

Database State Issues

A fully functioning SQL Server database has a "state" that it runs in, called ONLINE. In this state the database shows up as a normal icon in Enterprise Manager or Management Studio. There are other states, however, including OFFLINE, RESTORING, RECOVERING and so forth. If your database is in a state other than ONLINE, then you should check Books Online to find out more about why it is in one of these other conditions. Each condition has specific steps you should follow to correct the issue it represents, which I'll cover further in other articles here at InformIT.

Permissions Issues

I explain the basics SQL Server security more completely throughout this tutorial series, but I'll explain the basic login process here.

When a user tries to connect to a SQL Server database, they actually pass through two levels of security. The user must first exist as a server logon, and they also need access to a database through another user account. Most often the server and database account have the same name, but they are in fact different.

To make things even more complicated, SQL Server has two kinds of accounts. The first kind is created and maintained by SQL Server. In this case the user doesn't have to be recognized by the Windows system where the SQL Server platform is installed. If you're having connection issues, you need to make sure that the account is set up on both the server and the database as described in my series on security mentioned earlier.

In SQL Server 2000 and earlier, the control you have over the accounts created by SQL Server is pretty minor. You just have to ensure that the user is entering the name and password properly. In SQL Server 2005 and higher, you have a few more options, assuming the software is installed on a Windows 2003 server. In this configuration, you can have the accounts created on SQL Server follow some (but not all) of the same account policies that the server uses. In other words, you can lock out the account after a certain number of incorrect login attempts and so forth. If you have this configuration, you may need to check to make sure the user account isn't locked out.

Both versions of SQL Server can also leverage Windows accounts, whether they are created locally on the server or on an NTLM or Active Directory domain. In this case, you create the user on SQL Server by pointing to the Windows account name. In this configuration, you should make sure that the user isn't locked out of the Windows account before they try to access SQL Server. Remember, if an account is locked out during a Windows session, the user might not know it until they try to access a network resource, so don't take the fact that they are still able to use their system as an indication. Have them log out and back in to verify they aren't locked out of Windows.

Both of these cases have to do with the situation where some users can log in and others can't. If you're in a situation where no one can log in (including you), it still may have to do with permissions. Most people (for very good reasons) set the service accounts for SQL Server to a Windows account, rather than LocalSystem or NetworkSystem. If those accounts are part of the same policies that other user accounts are, then their passwords or durations might have locked them out as well. That means that they aren't able to log in, and so they aren't able to start SQL Server. You'll be able to see this when you try to start the SQL Server services and you continuously get a "log on denied" error in the Event log for those accounts.

Server Configuration Issues

All versions of SQL Server have various settings that allow clients to connect. When you try to connect to SQL Server, you will need to enable the same protocol the client uses. I’ve previously explained the tools to do that for SQL Server 2000, SQL Server 2005 and SQL Server 2008. In all of these, you have the ability to change the default TCP/IP port, and other settings for the various protocols installed on your server. You need to verify that the ports are set to what the clients expect.

In SQL Server 2005, the Surface Area Configuration (SAC) tool also controls even more basic settings, such as allowing remote connections. Check the previous link to ensure your settings are correct to allow clients in.

Client Issues

In addition to the server, database, network and configuration issues, you might have issues on the client-side. This can be anything from incorrect network settings to a firewall blocking the port the application uses. These kinds of issues are the easiest to locate, and the most difficult to solve.

They are easy to locate because you can verify the problem quickly by using the steps I mentioned earlier. Simply having the client logging on to another machine which works for another user will show you if the problem lies with the machine or the account.

They are hard to solve because a workstation's configuration is sometimes far more complex than a server. There are usually more drivers, user customizations and so forth. Also, any changes you make might damage the user's environment, so it is difficult to try things to fix the problem.

Your issue also may be with the configuration on the client. There are connection strings that you need to enter on most software to connect to your server. One of the most common connection errors is an incorrect connection string.

There's one other difficulty in working on a client's workstation. The first part of troubleshooting is to ask, "Was it working before?" If it was, the next thing to ask is "what changed?" We all know the answer. "Nothing", we hear, and we know that's not always true. Then it becomes a guessing game as you try to discover what has changed on the system.

This has been a short trip around your system, but the tips and information found here should help you discover the problem and point you to some possible corrections. The references below should help you find more information.

InformIT Articles and Sample Chapters

Jonathan Feldman has a good guide to Windows Network Troubleshooting that you can read for free.

Books and eBooks

If you’re just starting out with SQL Server, Eric Johnson has a good video tutorial, SQL Server Fundamentals for the Accidental DBA.

Online Resources

Microsoft has a great tutorial on connecting to SQL Server here.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020