Troubleshooting problems with SQL Server 2014 Management Studio
If you have problems with SQL Server 2014 Management Studio (SSMS 2014), review this
troubleshooting checklist to find potential solutions.
1. Install the latest SQL Server 2014 service pack.
Because many SQL Server 2014 Management Studio bugs were fixed in SQL Server service
packs, you should install the latest SQL Server service pack.
At the time this article was written the latest SQL Server 2014 service pack was
service pack 1. You can download the SQL Server 2014 service pack 1 at here:
https://www.microsoft.com/en-us/download/details.aspx?id=46694
2. The IntelliSense feature does not work correctly after you type Transact-SQL
statements in SSMS 2014.
This problem typically occurs when the connection between SQL Server and the client
is slow. This bug was first fixed in Cumulative Update package 1 for SQL Server 2014.
You can download the Cumulative Update package 1 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2931693
3. When you are designing a maintenance plan in SSMS 2014, if you try to move or
resize a task, the position of the mouse pointer unexpectedly moves to the
upper-left corner of the designer surface.
This is SSMS 2014 bug. This bug was first fixed in Cumulative Update package 4 for
SQL Server 2014. You can download the Cumulative Update package 4 for SQL Server 2014
at here:
https://support.microsoft.com/en-us/kb/2999197
4. The template script for creating SQL Azure databases in SSMS 2014 does not
include SQL Azure-specific options such as EDITION and SERVICE_OBJECTIVE.
This is SSMS 2014 bug. This bug was first fixed in Cumulative Update package 4 for
SQL Server 2014. You can download the Cumulative Update package 4 for SQL Server 2014
at here:
https://support.microsoft.com/en-us/kb/2999197
5. The error occurs when you use Office 15.0 Access Database Engine OLE DB Provider
as data source in SSMS 2014.
This is the error message text: “Could not connect source component”. This problem
occurs because when you use Microsoft Office 15.0 Access Database Engine OLE DB Provider
as the data source, the related table name cannot be found in the Access database.
This bug was first fixed in Cumulative Update package 5 for SQL Server 2014.
You can download the Cumulative Update package 5 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3011055
6. You cannot use new service tiers Basic, Standard and Premium when you deploy to
Windows Azure SQL Database in SSMS 2014.
This problem occurs because SSMS 2014 is not updated to match the current service tier
offerings. This bug was first fixed in Cumulative Update package 5 for SQL Server 2014.
You can download the Cumulative Update package 5 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3011055
7. The view indexes are not visible in the Object Explorer in SSMS 2014.
This is SSMS 2014 bug. This bug was first fixed in Cumulative Update package 5 for
SQL Server 2014. You can download the Cumulative Update package 5 for SQL Server 2014
at here:
https://support.microsoft.com/en-us/kb/3011055
8. The error occurs, when you try to use Clustered Shared Volumes (CSV) as a source
or destination in performing a backup or restore database activity in SSMS 2014.
This is the error message text: “Cannot access the specified path or file on the server”.
This bug was first fixed in Cumulative Update package 8 for SQL Server 2014. You can
download the Cumulative Update package 8 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3067836
To work around this problem, you can use Transact-SQL statements to perform the backup
or restore database activity in a new query window.
9. It takes longer time than expected to expand the Databases folder in Object
Explorer in SSMS 2014.
This problem occurs when you have a large number of databases in an instance of
SQL Server 2014. This bug was first fixed in Cumulative Update package 9 for
SQL Server 2014. You can download the Cumulative Update package 9 for SQL Server 2014
at here:
https://support.microsoft.com/en-us/kb/3075949
10. SQL Server Management Studio may cause an error message when you update a row of a
table in SQL Server 2014 by right-clicking the name of the table, and then clicking
“Open Table” in the Object Explorer.
This problem occurs when the table does not contain a primary key and the table contains
one or more columns of the text or ntext data type. To work around this problem, you
should create a new query window in SQL Server Management Studio and then use a SQL UPDATE
statement to update the row in the table. To resolve this problem, create a primary key
in the table.
11. The error 8152 may occur when you try to edit a SQL Server Agent job or a
maintenance plan by using SQL Server Management Studio.
The error 8152 indicates that string or binary data would be truncated. This problem
occurs when the name of the instance of SQL Server 2014 is longer than 30 characters.
To resolve this problem, install the latest SQL Server service pack.