Prakash Sundaresan

Prakash
Sundaresan

Prakash Sundaresan is a program manager with Microsoft's SQL Server Development Customer Advisory Team.

Articles
Memory Matters 2
Memory pressure can be a drain on your system’s resources. Microsoft’s SQL Server Customer Advisory Team shows you how to find and resolve memory pressure--before you decide you need more memory.
64-Bit Vs. 32-Bit Memory Management 1
Learn about memory-utilization differences between 64-bit and 32-bit SQL Server.
Optimizing Parameterization for Query Plan Reuse
Learn some reasons why your SQL Server might not be effectively reusing query plans.
Minding Memory 1
Understanding how SQL Server uses memory is an essential step in performance tuning. Members of Microsoft’s SQL Server Development Customer Advisory Team show you how they find information about SQL Server’s memory utilization.

Digital Magazine Archives

Browse back issues of SQL Server Pro, from January 2007 through the last issue published in April 2014. Find the back issues here.

 

From the Blogs
business people around a table and laptop
Oct 9, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 10: Dynamic Detection Gotcha #3

You can interject a SQL Server Job Step into your Jobs and have this new/injected Job Step do some checking for you. Here's a look at everything that’s involved in such an approach....More
Man holding a piece of paper with the word GOTCHA
Oct 7, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 9: Dynamic Detection Gotcha #2 3

Given that a USE statement is parsed before code is actually run, there are a few options that could be used as a around when it comes to detecting whether or not code should be run....More
iceberg
Oct 2, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 8: Dynamic Detection Gotcha #1 1

Learn about why the option of dynamically detecting whether or not to run a SQL Server Job at execution time is quite a bit more problematic than you might think....More
SQL Server Pro Forums

Get answers to questions, share tips, and engage with the SQL Server community in our Forums.

Sponsored Introduction Continue on to (or wait seconds) ×