totally agree, NEVER delete a LDF file.

But in your case i would try the following statement:

CREATE DATABASE [dbname] ON

(NAME = Name, FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\db.mdf')

FOR...

With SSIS is it very easy to read/write data to/from Excel.

So i would have a llok at that

/mSc

http://www.performanceduo.com

hmmm strange

and this is the errormessagt that you get from where ?? Visual Studio ?

What happens if you try to connect to ssis from ssms ?

why do you connect via NP ?

looks lige you are running the script on the server locally ?

"When i try to create a new PC" ?...

Can you explain this a little more ?

As I see it you have 2 options

Replication

or you could look at the new SS2008 feature CDC

/mSc

all maintenance plan data is stored in MSDB - you can delete them from there.

Hopefully this query can guide you in the right direction :

select *

from msdb.dbo.sysdbmaintplans

/mSc

If you do need the functionallity, and the like kills your performance.

I would then have a look at Fulltext Seach

/mSc

If I read your post right, the only thing you will use partiotioning for is to switch the fresh data into the main "table" everymorning...

Am i right, nothing mentioned about...

Not sure this is the answer you are looking for, but anyway.

I would delete the plan and create a new one, the time you spend on troubleshooting is way bigger...

another option could be to sample sys.sysprocesses once every x sec.

not as waterproof as profiler - but with les overhead

totally agree with "Mr or Mrs. 500"

If you'r running 2008, you could also have a look at CDC!

depending on your data - I would consider multiple filegroups, especially when talking restore/recovery

Piecemeal restore could come in handy for you if a crash happens

/mSC

well as Gail says, there's no east win on this one.

What I have done earlier is to a simple add a line in my procedures, and do some logging in...