Troubleshooting problems with linked servers in SQL Server 2017 If you have problems with linked servers in SQL Server 2017, review this troubleshooting checklist to find potential solutions. 1. Check that you have appropriate permissions to create linked servers. To create a linked server, you must have ALTER ANY LINKED SERVER permission. So, if you have no this permission, you...
Tag: troubleshoot
Troubleshooting SQL Server 2017 Roles
Troubleshooting SQL Server 2017 Roles If you have problems with SQL Server 2017 roles, review this troubleshooting checklist to find potential solutions. 1. The error 920 may occur when you modify the database script level. This error indicates that only members of the sysadmin role can modify the database script level. To resolve this problem, ensure that user, who modify...
Troubleshooting SQL Server 2017 Indexes
Troubleshooting SQL Server 2017 Indexes If you have problems with SQL Server 2017 indexes, review this troubleshooting checklist to find potential solutions. 1. You can get the error 602. This error indicates that SQL Server could not find an entry for index in a database. This error may occur if a stored procedure references a dropped table, or metadata is...
Troubleshooting problems with MDS in SQL Server 2017
Troubleshooting problems with MDS in SQL Server 2017 If you have problems with SQL Server 2017 Master Data Services (MDS), review this troubleshooting checklist to find potential solutions. 1. When you expand the Entities folder on the Manage Groups page in MDS, you may notice that it takes a long time to display all the entities under the folder. In...
Troubleshooting SQL Server 2017 Columnstore Indexes
Troubleshooting SQL Server 2017 Columnstore Indexes If you have problems with SQL Server 2017 columnstore indexes, review this troubleshooting checklist to find potential solutions. 1. You can get the error 980 when you try to load SQL Server 2017 database. This is the error message text: “SQL Server cannot load database ‘%.*ls’ because it contains a columnstore index.” This error...
Troubleshooting problems with deadlock in SQL Server 2017
Troubleshooting problems with deadlock in SQL Server 2017 If you have problems with deadlock in SQL Server 2017, review this troubleshooting checklist to find potential solutions. 1. Keep transactions as short as possible. This can be used to reduce deadlock, because problems with locking typically occurs when several long-running transactions execute concurrently in the same database. The shorter the transaction,...
Troubleshooting SQL Server 2017 full-text search
Troubleshooting SQL Server 2017 full-text search If you have problems with SQL Server 2017 full-text search, review this troubleshooting checklist to find potential solutions. 1. Ensure the user needs to create, alter or drop the full-text catalogs have appropriate permissions. To create a full-text catalog the user must have CREATE FULLTEXT CATALOG permission on the database, or must be a...
Troubleshooting SQL Server 2017 Merge Replication
Troubleshooting SQL Server 2017 Merge Replication If you have problems with SQL Server 2017 merge replication, review this troubleshooting checklist to find potential solutions. 1. Check that account the SQL Server and SQL Server Agent services runs under belongs to the Administrators local group and is a member of the Domain Users group. The LocalSystem account does not have network...
Troubleshooting SQL Server 2017 Transactional Replication
Troubleshooting SQL Server 2017 Transactional Replication If you have problems with SQL Server 2017 transactional replication, review this troubleshooting checklist to find potential solutions. 1. Check that you have sysadmin permissions on the SQL Server. Only members of the sysadmin server role can configure replication, so if you have not these permissions you cannot setting up or configure transactional replication....
Troubleshooting SQL Server 2017 Snapshot Replication
Troubleshooting SQL Server 2017 Snapshot Replication If you have problems with SQL Server 2017 snapshot replication, review this troubleshooting checklist to find potential solutions. 1. Check that you have sysadmin permissions on the SQL Server. Only members of the sysadmin server role can configure replication, so if you have not these permissions you cannot setting up or configure snapshot replication....