You've got a couple of problems here... your initial IF NOT EXISTS will successfully run the follow-up query only if there are NO records at all in AP_Job_Cost_Security22. ...

It's not as clean but you might try instead of using DBDDBC using backticks to execute command-line sqlcmd... I've experimented with the sql...

It depends really... if I don't have very complex needs for maintenance on the server, I'll use a maintenance plan. If I want something a little more fine-tuned...

As far as mailing goes, I've had some success using XP_SMTP (http://sqldev.net/xp/xpsmtp.htm) instead of SQL Mail. Usually if I have a job with 3 steps, I'll add a 4th...

There's a good article on this:

http://www.sqlservercentral.com/columnists/hji/trace.asp

You need to use dynamic SQL, it won't automatically parse your table name in.

create procedure set_interface_flag

@lnkey varchar(20),

@Tname varchar(25),

@fname varchar(25)

as

declare @sql nvarchar ( 4000 )

set @sql = 'update ' + @Tname...

Try this:

INSERT INTO SalesPerson (userName, CompanyId)

SELECT 'Hank', Id

FROM SellingCompany

WHERE CompanyName='Austin West-Side Lyncanthropic Association'

That will be fine so long as you don't have multiple Austin West-Side Lycanthropic Association values in SellingCompany.

If you want to put it on the same physical box you'll need to probably install a second instance. When you go through the SQL installation process, it will...

Hmm... it ate my first response, let me try again (shorter version):

EXEC() pulls out your dynamic SQL into a seperate context for execution. So things you declare in this...

could use COUNT_BIG()

SELECT COUNT_BIG(*) FROM table

I think the point of the question is that in 2005 maintenance plan tasks are executed all at once (though individual steps can be performed sequentially) based on a single...

The easiest way in my opinion would be to probably use two seperate derived tables. Derive them from BarCollectionTransactions each with the data you need.

Something like:

SELECTins.InsuranceGroupID as InsGroupID, bct_day.Date,...

I've seen it done by inserting all the data into a global temporary table (## prefix) like this:

CREATE TABLE ##tmp_table (

id_field INT IDENTITY(1,1)

,column1VARCHAR ( 50 )

,column2 VARCHAR ( 50 )

)

INSERT...

If you're trying to do it the way you describe that could be problemmatic. If you want to pivot data and you're using SQL Server 2005, you want to...

Just do an ALTER DATABASE mydb SET RECOVERY SIMPLE.