Articles

Technical Article

PASS 2009 Summit - Call for Speakers is Open

The call for speakers is open through midnight on April 10, 2009, so get busy submitting those abstracts! Work hard on the title and description, make it something that seems interesting and compelling for attendees. Expect the competition to be fierce...The call for speakers is open through midnight on April 10, 2009, so get busy submitting those abstracts! Work hard on the title and description, make it something that seems interesting and compelling for attendees. Expect the competition to be fierce...

You rated this post out of 5. Change rating

2009-03-24

950 reads

External Article

Finding the Causes of Poor Performance in SQL Server, Part 1

To tackle performance problems with applications, first use SQL Profiler to find the queries that constitute a typical workload: From the trace, spot the queries or stored procedures that are having the most impact. Then it's down to examining the execution plans and query statistics. You then see what effects you've had and maybe repeat the process. Gail explains all, in a two-part article.

2009-03-23

5,352 reads

Blogs

Why Developers Shouldn’t Have sysadmin access in SQL Server

By

 Why Developers Shouldn’t Have sysadmin access in SQL Server 7 reasons—and exactly what to do instead It...

A New Word: Ecstatic Shock

By

ecstatic shock – n. a surge of energy upon catching a glimpse from someone...

The CDO’s Playbook for AI Driven Decision Making

By

The New Arena of Leadership The role of the Chief Data Officer is no...

Read the latest Blogs

Forums

The Foundation of a Successful Doctoral Journey

By Ariel Wilson

Writing a PhD proposal is one of the most crucial steps in academic research....

sp_prepare and sp_execute vs sp_executesql

By rajemessage 14195

I have noticed sp_executesql also makes a single plan for a stmt with parameter...

Who am I?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Who am I?

Visit the forum

Question of the Day

Who am I?

If I want to track which login called a stored procedure and use the value in an audit, what function can I use to replace the xxx below?

create procedure AddNewCustomer
  @customername varchar(200)
AS
BEGIN
    DECLARE @added VARCHAR(100)
    SELECT @added = xxx

    IF @customername IS NOT NULL
      INSERT dbo.Customer
      (
          CustomerName,
          AddedBy 
      )
      VALUES
      (@customername, @added)
END

See possible answers