Articles

External Article

SQL Server Impersonation

SQL Server impersonation, or context switching, is a means to allow the executing user to assume the permissions of a given user or login until the context is set back, set to yet another user, or the session is ended. Deanna Dicken shows you two mechanisms for accomplishing this task and walks through some examples.

2010-02-25

2,388 reads

External Article

Microsoft SQL Server 2008 Analysis Services Consolidation Best Practices

This technical note describes the consolidation options, considerations, and best practices for Microsoft® SQL Server® 2008 Analysis Services that the SQL CAT team has derived from working with Analysis Services customers. In this technical note, we also discuss an Analysis Services load balancer solution that one of our internal customers uses to load balance queries from Microsoft Excel® and SQL Server Reporting Services clients across multiple query servers to increase query performance and provide availability.

2010-02-24

1,994 reads

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 Cikarang Tlpn/wa:085373737551

By SF Marble and Granite

Ruko Cikarang Plaza, Jl. Yos Sudarso No.5 Blok B, RW.6, Cikarang, Kec. Cikarang Utara,...

BCA KCP Ruko Jababeka Tlpn/wa:085373737551

By SF Marble and Granite

Ruko Permata Junction, Jl. Jababeka Raya Blok A2-3, Cikarang, Cikarang Sel., Kabupaten Bekasi, DKI...

BCA KCP Taman Galaxi Tlpn/wa:085373737551

By SF Marble and Granite

Jl. Surya Raya Jl. Taman Galaxy Raya No.31 blok A, RT.001/RW.014, Jaka Setia, Kec....

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