No. You could try inserts to a logging table or use sp_oa... items to call and talk to a text file to write data to (creates a high failure point...

Not sure what you need you message seems chopped. Weird it was chopped when viewed from the house. Did the last edited remark go away?

Do you mean for admin duties or client editing? If for admin I suggest the best tool is still EM although some products offer features of EM with a bit...

I do believe it is slightly wrong but the right concept.

Here is the info from MS. Found at http://support.microsoft.com/default.aspx?scid=kb;EN-US;224071

(Note wat is says to do before reattach.)

I agree w/Oskar, I personally find none of these appealing. However the box desn't really say SQL to me either as well. But the question is what are you trying...

The best tool at your disposal is Profiler, set it to monitor the server for the following events should give you an idea.

Database - Data File Auto Grow

Database - Log...

Pretty much the who is SQL Server, any action that generates temp tables such as temp table creation, order by, group by, some bulk inserts and other items can impact...

I tried this and got not issues, also tried with creating the table as a whole and adding office at the end.

declare @fmt as varchar(1)

set @fmt = 'b'

if object_id('tempdb..#process') is...

Another option

SELECT

 itemno,

 SUM((CASE WHEN YEAR(shipdate) = 2003 THEN qty ELSE 0 END)) [2003qty],

 SUM((CASE WHEN YEAR(shipdate) = 2003 THEN sales ELSE 0 END)) [2003sales],

 SUM((CASE WHEN YEAR(shipdate) = 2002 THEN...

I prefer this method.

SELECT

DATEADD(d,-1,DATEADD(m,datediff(m,0,getdate()),0)) as LastDayPreviousMonth,

DATEADD(m,datediff(m,0,getdate()),0) as FirstDayOfCurrentMonth,

DATEADD(m,1,DATEADD(m,datediff(m,0,getdate()),0)) as FirstDayOfNextMonth

Oops, thanks Mike, meant once per statement when I said per transaction.

Ok I am not going to ding you on concept as I have tried this before. However here is a good starting article for the reasons why this is bad...

I agree a very good suggestion.

I believe this is an issue in the compile portion of the query engine in that it recognizes the CREATE TABLE #process and has built in memory then sees again...

First you must understand that NULL is an unknown value so when you conditionally exclued data the value cannot be determined and could in fact be the value to exclude.

If...