alzdba

  • Interests: family, mantrailing / dogs, riding my motorbike, volleyball

SQLServerCentral Article

Getting SQLAgent to Respond Faster

One limitation of SQLAgent is that granularity to which you can schedule jobs: every minute. Sometimes there are things that you would like to happen more frequently, like alerting. Johan Bijnens brings us a technique for getting your SQL Agent to respond to alerts in as little as every 10 seconds.

You rated this post out of 5. Change rating

2007-08-16

5,799 reads

Technical Article

help to tighten use of  cmdshell  or sp_start_job

-- The goal is to avoid the use of sp_start_job in an application. So we have the application use RAISERROR to activate the job.--  1) because you can only start jobs you own--  2) we don't want to open the cmdshell to everyone--  3) we want control regarding jobs that run on our server.--  4) […]

(1)

You rated this post out of 5. Change rating

2007-05-31 (first published: )

2,166 reads

Technical Article

Detect invalid FK-data after using "WITH NOCHECK"

In situations where FK's have been created using the "WITH NOCHECK" option you can get into troubles because the FK-data is not checked ! (so there may be invalid data in the FK-column !)E.g. ALTER TABLE [dbo].[mytable] WITH NOCHECK add constraint [FK__USED_RESO__Actio__1162CF5F] FOREIGN KEY ( Action_Type ) REFERENCES [dbo].[Action_Types] ( Action_Type ) BOL states "... […]

You rated this post out of 5. Change rating

2007-05-29 (first published: )

545 reads

SQLServerCentral Article

Adventures With Service Broker

Service Broker is one of those new SQL Server 2005 features that doesn't get much press, but is extremely interesting from a software architect perspective. The much talked about service oriented architecture (SOA) can make use of Service Broker and new author Johan Bijnens brings us a look at this subsystem.

You rated this post out of 5. Change rating

2007-04-16

9,766 reads

Blogs

Flyway Tips: AI Deployment Script Descriptions

By

With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...

A New Word: Fawtle

By

fawtle – n. a weird little flaw built into your partner that somehow only...

Post-quantum key exchange – Insurance policy for your packets

By

AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...

Read the latest Blogs

Forums

Where Your Value Separates You from Others

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Where Your Value Separates You...

Fixing the Error

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Fixing the Error

T-SQL in SQL Server 2025: Encoding Functions

By Steve Jones - SSC Editor

Comments posted to this topic are about the item T-SQL in SQL Server 2025:...

Visit the forum

Question of the Day

Fixing the Error

On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:

SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error?

See possible answers