Stefan Steiger ststeiger

Alle: =IIF(COUNTROWS("SEL_Standort").Equals(Parameters!in_standort.Count),"Alle","Nicht Alle")

This is how to fix this error:
An HTTPS binding already exists for the specified IP address and port combination!

netsh http show sslcert

if too long

netsh http show sslcert > sslcert.txt


	Simply convert:
	ffmpeg -i input.avi output.mp4

	Simply convert, but only the left half of the screen(s):
	ffmpeg -i input.avi -filter_complex "[0:v]crop=iw/2:ih:0:0,scale=iw:ih[out]" -map "[out]" output.mp4


	Simply convert, but only the right half of the screen(s):
	ffmpeg -i input.avi -filter_complex "[0:v]crop=iw/2:ih:ow:0,scale=iw:ih[out]" -map "[out]" output.mp4

	USE master
	GO

	ALTER DATABASE database_name SET SINGLE_USER WITH ROLLBACK IMMEDIATE

	GO

	ALTER DATABASE database_name SET MULTI_USER WITH ROLLBACK IMMEDIATE


	SELECT
	t.[text], qs.creation_time
	FROM sys.dm_exec_cached_plans AS p
	CROSS APPLY sys.dm_exec_sql_text(p.plan_handle) AS t
	JOIN sys.dm_exec_query_stats qs ON p.plan_handle = qs.plan_handle
	-- WHERE t.[text] LIKE N'%something unique about your query%';
	WHERE t.[text] LIKE N'%CTE%'
	-- AND t.text LIKE '%APP-APERTUR%'
	ORDER BY qs.creation_time DESC


	CREATE TABLE IF NOT EXISTS named_colors
	(
	nc_val int NOT NULL
	,nc_r tinyint NULL
	,nc_g tinyint NULL
	,nc_b tinyint NULL
	,nc_name varchar(50) NOT NULL
	,nc_hex varchar(7) NULL
	,CONSTRAINT pk_named_colors PRIMARY KEY ( nc_name )


	function createHTMLFromJSONML(jsonML)
	{
	if (!Array.isArray(jsonML) \|\| jsonML.length === 0)
	{
	return '';
	}

	const [tag, attributes, ...children] = jsonML;

	<!DOCTYPE html>
	<html lang="en" xmlns="http://www.w3.org/1999/xhtml">
	<head>
	<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
	<meta charset="utf-8" />
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

	<meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate, max-age=0">
	<meta http-equiv="Pragma" content="no-cache">
	<meta http-equiv="expires" content="Tue, 01 Jan 1980 1:00:00 GMT" />

	The SQL Browser service typically listens on UDP port 1434.
	When a client application requests connection information for a specific instance name,
	it sends a query to the SQL Browser service on port 1434,
	which then responds with the port number associated with the requested instance name.

	If the UDP port 1434 is blocked by a firewall, the instance name to port lookup may fail,
	resulting in connection issues when using instance names.
	In such cases, connecting using the port number directly (e.g., SQL17,2673)
	might work if the firewall allows traffic on the specific port.


	namespace ExportDatabase
	{


	class AmHoliday
	{


	public static System.DateTime Thanksgiving(int year)