Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the copy-the-code domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/pcx3.com/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pb-seo-friendly-images domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/pcx3.com/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the johannes domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/pcx3.com/wp-includes/functions.php on line 6121
⚠️ SQL server: Terminate database connections - PC✗3
⚠️ SQL server: Terminate database connections

⚠️ SQL server: Terminate database connections

Each application taht uses your SQL Server database creates a connection on the database and this connection continues unless the session is killed or terminated privately within the application. A similar connection is established even for each query window in SQL Server Management Studio.

These active connections may cause us problems in many processes, especially restoration operations. Looped applications can occupy our server unnecessarily. We may need to terminate it specifically.

In such cases, all connections installed in that database are terminated with the following script. It is enough to write the name of our database, and which connections we want to terminate.

USE master
DECLARE @dbname sysname
SET @dbname = '<dbnamehere>'
DECLARE @spid int
SELECT @spid = min (spid) from master.dbo.sysprocesses where dbid = db_id (@dbname)
WHILE @spid IS NOT NULL
BEGIN
EXECUTE ('KILL' + @spid)
SELECT @spid = min (spid) from master.dbo.sysprocesses where dbid = db_id (@dbname) AND spid> @spid
END

Hopefully it benefits your business…

whoami
Stefan Pejcic
Join the discussion

I enjoy constructive responses and professional comments to my posts, and invite anyone to comment or link to my site.