Newsgroups: microsoft.public.sqlserver.server
From: chang...@online.microsoft.com (Charles Wang[MSFT])
Date: Wed, 23 Aug 2006 14:20:33 GMT
Local: Wed, Aug 23 2006 10:20 am
Subject: Re: 'Troubleshooting Performance Problems in SQL Server 2005" white paper.
Hi Olivier,
My steps are as following: 1. Create the sp_addcolumn stored procedure: create proc dbo.add_column ( @add_stmt varchar(500) output, @find varchar(100)=NULL, @cols_containing varchar(500)=NULL, @col_stmt varchar(max)) as -- -- This stored procedure is provided "AS IS" with no warranties, and -- confers no rights. -- Use of included script samples are subject to the terms specified at -- http://www.microsoft.com/info/cpyright.htm -- -- T. Davidson -- @add_stmt is the result passed back to the caller -- @find is a keyword from @cols_containing -- @cols_containing is the list of keywords to include in the report -- @col_stmt is the statement that will be compared with @find. -- If @col_stmt contains @find, include this statement. -- set @add_stmt = @col_stmt -- declare @length int, @strindex int, @EOS bit if @cols_containing is NULL begin select @add_stmt=@col_stmt return end select @add_stmt = '', @EOS = 0 while @add_stmt is not null and @EOS = 0 2. Create the stored procedure dbo.get_indexstats without modification. You can try my steps and see whether or not the issue will occur. Sincerely, You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| ||||||||||||||