SQL Server And MSBI https://docs.microsoft.com/archive/blogs/sql_server_and_msbi/feed.xml Wed, 17 Apr 2019 03:51:56 GMT en-US hourly 1 Asynchronous Processing with SQL Server Service Broker - A case Study https://docs.microsoft.com/archive/blogs/sql_server_and_msbi/asynchronous-processing-with-sql-server-service-broker-a-case-study Wed, 18 Mar 2015 06:47:12 GMT https://blogs.msdn.microsoft.com/sql_server_and_msbi/2015/03/18/asynchronous-processing-with-sql-server-service-broker-a-case-study/ How about an asynchronous queuing mechanism which doesn’t entail a customary two phase commit ?

How about, not worrying about dead locks,transactions, blockings, waits ?

How about scaling out/up your systems without any extra line of codes ?

How about not losing your peace of mind over data integrity/Consistency ?

How about simply adding your order to a queue and the system confirms the order with the order confirmation popping into your inbox ?

SQL Server answers it all with remarkable two words – “Service Broker” !

 

The vblog discusses a case study in < 15 mins, for an online ecommerce site, on how the orders can be asynchronously processed and confirmation emails be sent, all with the help of SQL Server Service Broker.

[View:https://www.youtube.com/watch?v=jXhTE5BY8eA]

]]> Error: Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set for the connection. https://docs.microsoft.com/archive/blogs/sql_server_and_msbi/error-heterogeneous-queries-require-the-ansi_nulls-and-ansi_warnings-options-to-be-set-for-the-connection Wed, 18 Mar 2015 01:49:00 GMT https://blogs.msdn.microsoft.com/sql_server_and_msbi/2015/03/18/error-heterogeneous-queries-require-the-ansi_nulls-and-ansi_warnings-options-to-be-set-for-the-connection/ Last week sometime, working on a very tight project with stringent deliverables and deadlines, its just when you don't need a reason you have one, a show stopper. And your job is failing. The error quite obscure : "Error: Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set for the connection." Of the internet/people/voices/opinions and some ON/OFF with no logical reason or supporting workable evidence. It didn't work !

I discovered something quite trivial, yet unknown.

To start with,

EXECUTE usp<<Procedure>>  @LinkedServerName =<<LinkedServerName>> ,@SourceDatabaseName =<<SrcDBName>>,@SourceTableName=<<SrcTableName>> ,@TargetTableName = <<TargetTblName>>

The code was trying to call a Proc to connect to a Source and populate the target data, and was failing with the error message in context.

The procedure already had the 3 sacred declarations.

CREATE usp_Proc @Pram1 INT  = 0
,@Pram1 VARCHAR(10) = NULL
AS
BEGIN
    BEGIN TRY
        SET ANSI_NULLS ON
  SET QUOTED_IDENTIFIER ON
  SET ANSI_WARNINGS ON
        SET NOCOUNT ON;

.

.

EXECUTE usp<<Procedure>>  @LinkedServerName =<<LinkedServerName>> ,@SourceDatabaseName =<<SrcDBName>>,@SourceTableName=<<SrcTableName>> ,@TargetTableName = <<TargetTblName>>

I tried to play with it, turning to ON/OFF hoping that the job would run, until I bumped into, Stored Procedure Properties

The Properties for the Proc in question was

The ANSI_NULLs ans Quoted Identifier Properties were SET to FALSE. To SET the same, I executed the PROC ALTER script with the Properties ADDed AS ON

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER PROCEDURE
@Pram1 INT  = 0
,@Pram1 VARCHAR(10) = NULL
AS
BEGIN
    BEGIN TRY
        SET ANSI_NULLS ON
  SET QUOTED_IDENTIFIER ON
  SET ANSI_WARNINGS ON
        SET NOCOUNT ON;

With these SET to TRUE, the job/code succeeded and the issue was resolved.

Hope it helps.

 

]]> Comparing Isolation Levels in SQL Server https://docs.microsoft.com/archive/blogs/sql_server_and_msbi/comparing-isolation-levels-in-sql-server Tue, 17 Mar 2015 06:59:00 GMT https://blogs.msdn.microsoft.com/sql_server_and_msbi/2015/03/17/comparing-isolation-levels-in-sql-server/ Transactions form a very important concept for any significant data operations. Keeping your data isolated and abiding by the ACID properties form the core of the transaction concept. This vblog is my take to SQL Server READ COMITTED, REPEATABLE READ and SERIALIZABLE isolation levels.

[View:https://www.youtube.com/watch?v=kTU3PtP_pkg]

 

]]>