-search all databases CREATE OR ALTER PROC tools.findInName (@searchstring VARCHAR(200)) AS BEGIN SET NOCOUNT ON DECLARE @results TABLE ( [search_term] VARCHAR(255), [database_name] VARCHAR(255), [schema_name] VARCHAR(255), [object_Name] VARCHAR(255), [type_desc] VARCHAR(255) ) DECLARE @dbname sysname; DECLARE @actualsearchstring VARCHAR(200); SET @actualsearchstring = REPLACE(@searchstring,'_','/_') DECLARE @dsql nvarchar(max) = ' SELECT ''' +@searchstring + ''' AS [search_term] ,DB_NAME() AS [database_name] ,TABLE_SCHEMA ,TABLE_NAME ,TABLE_TYPE FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME LIKE ''%'+@actualsearchstring+'%'' ESCAPE ''/'' UNION ALL SELECT ''' +@searchstring + ''' AS [search_term] ,DB_NAME() AS [database_name] ,ROUTINE_SCHEMA ,ROUTINE_NAME ,ROUTINE_TYPE FROM INFORMATION_SCHEMA.ROUTINES WHERE ROUTINE_NAME LIKE ''%'+@actualsearchstring+'%'' ESCAPE ''/'' '; DECLARE @execCommand nvarchar(max); DECLARE dbs CURSOR STATIC LOCAL FORWARD_ONLY READ_ONLY FOR SELECT name FROM sys.databases (NOLOCK) OPEN dbs; FETCH NEXT FROM dbs INTO @dbname; WHILE @@FETCH_STATUS = 0 BEGIN SET @execCommand = 'EXEC ' + QUOTENAME(@dbname) + '.sys.sp_executesql @dsql'; INSERT @results EXEC sys.sp_executesql @execCommand, N'@dsql nvarchar(max)', @dsql FETCH NEXT FROM dbs INTO @dbname; END CLOSE dbs; DEALLOCATE dbs; SELECT * FROM @results END GO EXEC tools.findInName '_'
Tuesday, 31 July 2018
findInName - Stored Procedure to search all object names
TSQL - Searching for Escaped Characters
Use the ESCAPE keyword to define a character to use to escape a literal.
The _ underscore cannot usually be searched, to do so escape it like this.
SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME LIKE '%/_%' ESCAPE '/'
findInCode - Stored Procedure to search code in all databases for a string
--search all databases CREATE OR ALTER PROC tools.findInCode (@searchstring VARCHAR(200)) AS BEGIN SET NOCOUNT ON DECLARE @results TABLE ( [searchTerm] VARCHAR(255) ,[databaseName] VARCHAR(255) ,[schemaName] VARCHAR(255) ,[objectName] VARCHAR(255) ,[typeDesc] VARCHAR(255) ) DECLARE @dbname sysname; DECLARE @dsql nvarchar(max) = ' SELECT ''' +@searchstring + ''' AS [search_term] ,DB_NAME() AS [databaseName] ,SCHEMA_NAME(schema_id) as schemaName ,o.name AS ObjectName ,o.type_desc AS typeDesc FROM sys.sql_modules m (NOLOCK) INNER JOIN sys.objects o (NOLOCK) ON m.object_id = o.object_id WHERE m.definition LIKE ''%'+@searchstring+'%'' '; DECLARE @execCommand nvarchar(max); DECLARE dbs CURSOR STATIC LOCAL FORWARD_ONLY READ_ONLY FOR SELECT name FROM sys.databases (NOLOCK) OPEN dbs; FETCH NEXT FROM dbs INTO @dbname; WHILE @@FETCH_STATUS = 0 BEGIN SET @execCommand = 'EXEC ' + QUOTENAME(@dbname) + '.sys.sp_executesql @dsql'; INSERT @results EXEC sys.sp_executesql @execCommand, N'@dsql nvarchar(max)', @dsql FETCH NEXT FROM dbs INTO @dbname; END CLOSE dbs; DEALLOCATE dbs; SELECT * FROM @results END GO EXEC tools.findInCode 'findme'
Friday, 27 July 2018
Database Mirroring : TSQL Health Scripts
-- Dynamic Managment View of configuration information SELECT db_name(sd.[database_id]) AS [Database Name] ,sd.mirroring_state AS [Mirror State] ,sd.mirroring_state_desc AS [Mirror State] ,sd.mirroring_partner_name AS [Partner Name] ,sd.mirroring_role_desc AS [Mirror Role] ,sd.mirroring_safety_level_desc AS [Safety Level] ,sd.mirroring_witness_name AS [Witness] ,sd.mirroring_connection_timeout AS [Timeout(sec)] FROM sys.database_mirroring AS sd WHERE mirroring_guid IS NOT null ORDER BY [Database Name];
-- history of all mirored transactions in last 2 hours USE msdb; EXEC sp_dbmmonitorresults DatabaseName, 2, 0;
--os performance counters about mirroring SELECT *,[counter_name] as CounterName,[cntr_value] as CounterValue FROM sys.dm_os_performance_counters WHERE [object_name] LIKE ('%Database Mirroring%') AND [instance_name]='mirroredDatabase'
Sunday, 22 July 2018
Linked Server Setting - Promotion of Distributed Transactions
This error occured when I tried to access a stored proedure via a linked server.
Getting the results worked fine, simply executing the stored procedure.
But putting the results into a temporary table meant it became a 'distributed transaction'
OLE DB provider "SQLNCLI10" for linked server "SERVERNAME" returned message "The partner transaction manager has disabled its support for remote/network transactions.".
Msg 7391, Level 16, State 2, Line 12
The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "SERVERNAME" was unable to begin a distributed transaction.
Both servers were already running the Distributed Transaction Coordinator (DTC) service.
Multiple posts suggest tuning the security of DTC, but I eventually found the solution was much simpler. Like the setting for Remote Procedure calls RPC, it turned out to be a property of the linked server itself, 'Enable Promotion of Distributed Transactions'.
The default for 'Enable Promotion of Distributed Transactions' is TRUE, setting it to FALSE enabled my code to run.
Getting the results worked fine, simply executing the stored procedure.
EXEC [SERVERNAME].[DatabaseName].[SchemaName].[myStoredProcedure]
But putting the results into a temporary table meant it became a 'distributed transaction'
CREATE TABLE ##tempTable (column1, column2...) INSERT INTO ##tempTable EXEC [SERVERNAME].[DatabaseName].[SchemaName].[myStoredProcedure]
OLE DB provider "SQLNCLI10" for linked server "SERVERNAME" returned message "The partner transaction manager has disabled its support for remote/network transactions.".
Msg 7391, Level 16, State 2, Line 12
The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "SERVERNAME" was unable to begin a distributed transaction.
Both servers were already running the Distributed Transaction Coordinator (DTC) service.
Multiple posts suggest tuning the security of DTC, but I eventually found the solution was much simpler. Like the setting for Remote Procedure calls RPC, it turned out to be a property of the linked server itself, 'Enable Promotion of Distributed Transactions'.
The default for 'Enable Promotion of Distributed Transactions' is TRUE, setting it to FALSE enabled my code to run.
Thursday, 19 July 2018
Renaming a Linked Server
Simple but very helpful as scripting out a linked server won't include the password information.
EXEC master.dbo.sp_serveroption @server=N'OLDNAME', @optname=N'name', @optvalue=N'NEWNAME'
Sunday, 8 July 2018
Trace Flag 7470
Trace flag 7470 works in SQL 2017! I'm always a little reluctant to use trace flags, especially after reading that Trace flags were becoming redundant due to more database level settings.
Anyway, I've eliminated the Sort operator spilling to tempdb by applying 7470.
Note, the documentation says it doesn't apply to SQL 2017, but I had it on good authority that it would,
Trace Flag 7470 : Fix operator spills to tempdb
Anyway, I've eliminated the Sort operator spilling to tempdb by applying 7470.
Note, the documentation says it doesn't apply to SQL 2017, but I had it on good authority that it would,
Trace Flag 7470 : Fix operator spills to tempdb
Subscribe to:
Posts (Atom)