Introduction Data safe ensured by some special kind of mechanisms in modern database providers. I like the way of MSSQL is designed and it is still improvising or shaping better in all aspects. In MSSQL, if we need to hide business logic of stored procedure, then stored procedure encryption is comes handy with MSSQL in order to ensure data security. By the way decryption is not straight forward in MSSQL. Let's see what are all the impacts of stored procedure encryption and see how to overcome those. Encrypt Stored Procedure Stored procedure encryption only restrict anyone from viewing or editing. It will still allow us to execute the stored procedure with all needed parameter values. We can "CREATE OR ALTER PROC" stored procedure with "WITH ENCRYPTION" to encrypt stored procedure. USE [pubs] GO SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE OR ALTER PROCEDURE [dbo].[reptq1] WITH ENCRYPTION AS select case when grouping(pub_id) = 1 then 'ALL'
Introduction We are in the new world of microservices and cross-platform applications which will be supported for multiple platforms and multiple heterogeneous teams can work on the same application. I like ASP.NET Core by the way its groomed to support modern architecture and adhere to the software principles. I am a big fan of dot net and now I become the craziest fan after seeing the sophisticated facility by dot net core to support infrastructure level where we can easily perform vertical and horizontal scaling. It very important design aspect is to keep things simple and short and by the way, RESTFul applications are build and it is a powerful mantra for REST-based application and frameworks. Some times we need to overrule some principles and order to handle some situations. I would like to share my situation of handling HTTP long polling to resolve the ASP.Net core 2 mins issue. What is HTTP Long polling? In the RESTFul term, when a client asks for a query from the serv