External Article

Using Dynamic SQL in Stored Procedures

Dynamic SQL allows stored procedures to “write” or dynamically generate their SQL statements. The most common use case for dynamic SQL is stored procedures with optional parameters in the WHERE clause. These are typically called from reports or screens that have multiple, optional search criteria. This article describes how to write these types of stored procedures so they execute well and resist SQL injection attacks.

Technical Article

Mouse Clicks, Reactive Extensions and StreamInsight Mashup

I had an hour spare this afternoon so I wanted to have another play with Reactive Extensions in .Net and StreamInsight. I also didn’t want to simply use a console window as a way of gathering events so I decided to use a windows form instead. The task I set myself was this. Whenever I click on my form I want to subscribe to the event and output its location to the console window and also the timestamp of the event.

Blogs

Overcoming Imposter Syndrome: A Plan

By

My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...

Advice I Like: Celebrate Success

By

“On the way to a grand goal, celebrate the smallest victories as if each...

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

Read the latest Blogs

Forums

BCA KCP LembangTelepon083179431638

By true protein powder

WhatsApp083179431638Jl. Pasar Baru 8, Lembang, Kec. Lembang, Kabupaten Bandung Barat, Jawa Barat 40391

BCA KCP Grand Cempaka Mas Telp:08213111109

By innosys

Ruko Mega Grosir Cempaka Mas, Blk. A Jl. Letjen Suprapto No.5 A/7, Sumur Batu,...

BCA KCU SURYOPRANOTO Telp:cs.(0821)8171955

By telediousnom7887

Whatsapp:08218171955 Jl. Suryopranoto No.40, Petojo Utara, Kecamatan Gambir, Kota Jakarta Pusat, Daerah Khusus Ibukota...

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers