Skip to content

Commit b644c2a

Browse files
authored
More re-writes
1 parent 8862159 commit b644c2a

1 file changed

Lines changed: 4 additions & 32 deletions

File tree

support/sql/database-engine/startup-shutdown/sql-server-agent-crashes-upon-start.md

Lines changed: 4 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -97,52 +97,24 @@ For information about the ODBC driver requirements for different versions of SQL
9797
### Solution
9898

9999
1. To check if the SQL Server ODBC driver is missing, run one of the following commands in an elevated Command Prompt window or PowerShell:
100-
1. Command prompt:
100+
1. Command prompt to launch ODBC Data Source Administrator:
101101

102102
```cli
103103
odbcad32.exe
104104
```
105105
106-
1. Check if the expected SQL Server ODBC driver is there by comparing to the following table [SQL Server versions and ODBC and OLE DB drivers](/sql/connect/connect-history#sql-server-versions-and-odbc-and-ole-db-drivers). The table lists the SQL Server ODBC driver version shipped with each SQL Server engine and used by SQL Server Agent to connect to SQL Server engine.
107-
108-
1. PowerShell:
106+
1. PowerShell cmd-let:
109107
110108
```powershell
111109
Get-OdbcDriver
112110
```
113111
114-
This command returns an output that resembles the following example:
115-
116-
```output
117-
Name : SQL Server
118-
Platform : 64-bit
119-
Attribute : {APILevel, FileUsage, Driver, ConnectFunctions...}
120-
121-
Name : SQL Server Native Client 11.0
122-
Platform : 64-bit
123-
Attribute : {Driver, APILevel, FileUsage, Setup...}
124-
125-
Name : Microsoft Access Driver (*.mdb, *.accdb)
126-
Platform : 64-bit
127-
Attribute : {Driver, APILevel, FileExtns, FileUsage...}
128-
129-
Name : Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)
130-
Platform : 64-bit
131-
Attribute : {Driver, APILevel, FileExtns, FileUsage...}
132-
133-
Name : Microsoft Access Text Driver (*.txt, *.csv)
134-
Platform : 64-bit
135-
Attribute : {Driver, APILevel, FileExtns, FileUsage...}
136-
137-
Name : Microsoft Access dBASE Driver (*.dbf, *.ndx, *.mdx)
138-
Platform : 64-bit
139-
Attribute : {Driver, APILevel, FileExtns, FileUsage...}
140-
```
112+
1. Check if the expected SQL Server ODBC driver is there by comparing to the following table [SQL Server versions and ODBC and OLE DB drivers](/sql/connect/connect-history#sql-server-versions-and-odbc-and-ole-db-drivers). The table lists the SQL Server ODBC driver version shipped with each SQL Server engine and used by SQL Server Agent to connect to SQL Server engine.
141113
142114
If the SQL Server ODBC driver isn't listed in the output of the `Get-OdbcDriver` command, then the driver is missing.
143115
144116
1. Check if the ODBC driver for SQL Server is present
145-
1. If the driver is missing, go to the next step.
117+
1. If the driver is missing, go to the next step [ODBC driver is present](#sql-server-odbc-driver-is-present)
146118
1. If the driver is missing, go to [ODBC driver is missing](#sql-server-odbc-driver-is-missing)
147119
148120
#### SQL Server ODBC driver is present

0 commit comments

Comments
 (0)