Christos Polydorou

Moving on to the next article about Microsoft Operations Manager Suite, we're going to take a look on a solution for Microsoft SQL servers. The SQL Health Check solution will provide useful information about the status of your SQL servers regarding security, compliance, availability, performance and many other aspects. As you may see below, I have a lot of recommendations for my lab servers, including the accounts used by the SQL services, the performance of the tempdb and even the power settings on the servers! Two of the below stand out, the suggestion to check the logins on the servers - since they are members of an availability group and missing logins can cause application downtime and the suggestion to limit the memory of the SQL server in order to avoid consuming memory needed by the operating system. The solution also provides information about the upgrade and migration status, change management and operations and monitoring. Here, I'm warned that R

Today's topic? Microsoft SQL Server Linked Servers! Linked Servers are objects created in Microsoft SQL Server that allow queries to access data on other database servers such as Oracle. There are many reasons why a query that uses a linked server may fail with driver and network being the most common ones. When I need to troubleshoot scenarios like the above, I usually start with testing the linked server connectivity with the query below. 1 2 3 4 5 6 7 8 9 10 declare @ srv nvarchar( 128 ), @ retval int ; set @ srv = ‘ my_linked_server ' ; begin try exec @ retval = sys.sp_testlinkedserver @ srv; end try begin catch set @ retval = sign( @@ error); end catch; if @ retval <> 0 raiserror( ‘ Failed to connect to server ! ’ , 16 , 2 );