mhitza

This document was based on my local [GNU Guile][1]-3.0.5 setup. I'm not sure if it works as is with an older version of GNU Guile.

Because of a [dependency in Fedora][2] I had to compile GNU Guile from source release. As such, in your local setup the paths will differ. This is only relevant when defining the GUILE shell variable, and referencing the tags file in the vimrc.

Note that when building GNU Guile from source be sure that you have the readline-devel (or distro equivalent package) installed. That way the ./configure step will pick that up, and the ice-9 readline module will be usable.

tcartwright

/*
	Tim C: This query can be used as a normal query, or it can also be used to import into an OUTLOOK calendar so 
	you can visualize your backups. Similar to https://dbatools.io/timeline/
	
	RECOMMENDATIONS:
		1) You should import into a CUSTOM blank excel calendar
		2) You should not import TLOG backups, as that will utterly bloat the calendar
		
	******************************************************************************************
	TO CREATE A NEW CALENDAR:

tcartwright

 [CmdletBinding()]
 Param (
	[Parameter(Mandatory=$true, ValueFromPipeline = $true, ValueFromPipelineByPropertyName = $true)]
	[string] $path
 )

Clear-Host

[xml]$plan = Get-Content -Path ($path.TrimStart('"').TrimEnd('"'))

tcartwright

 [CmdletBinding()]
 Param (
	[Parameter(Mandatory=$true, ValueFromPipeline = $true, ValueFromPipelineByPropertyName = $true)]
	[string] $ServerInstance,

	[Parameter(Mandatory=$true, ValueFromPipeline = $true, ValueFromPipelineByPropertyName = $true)]
	[string] $planHandle
 )

 <#

tcartwright

/*
	Author: Tim Cartwright, Daniel Berber
	Purpose: To get the compile gateway counts out of sql server. Most likely if you are hitting gateway issues, 
		you are seeing RESOURCE_SEMAPHORE_QUERY_COMPILE wait stats. The gateways act as a sort of funnel. 
		The more compile memory a plan needs, the bigger the gateway required. If the number of queries being compiled
		for that gate way exceed the available count then the following queries will get stuck waiting with the 
		RESOURCE_SEMAPHORE_QUERY_COMPILE wait stat. 


	If you are using SQL Server 2016 or greater you can use: sys.dm_exec_query_optimizer_memory_gateways

tcartwright

Converted into a module: https://github.com/tcartwright/tcdbtools

PS Gallery link: https://www.powershellgallery.com/packages/tcdbtools/

https://github.com/tcartwright/tcdbtools/blob/main/tcdbtools/sql/FindInvalidSettings.sql

xzilla

\q
/*

What's New In PostgreSQL 12: All Demo Edition

Robert Treat (@robtreat2) - v5 - 2020-05-23


Requirements:
Postgres 12 

tcartwright

Converted into a module: https://github.com/tcartwright/tcdbtools

PS Gallery link: https://www.powershellgallery.com/packages/tcdbtools/

dazfuller

MIT License

Copyright (c) 2018 Darren Fuller

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

kmoppel

select
  test,                                                                   
  query::char(48),
  instance,
  --scale,
  --clients,
  round(mean_time::numeric, 4) mean_time,
  round(stddev_time::numeric, 4) stddev_time,
  round(((mean_time - mean_time_lag)::numeric / mean_time::numeric )*100, 1) as mean_time_diff,
  round(((stddev_time - stddev_time_lag)::numeric  / stddev_time::numeric )*100, 1) as stddev_time_diff