That worked.

Sent results to the parties who requested it, let's hope they like it. 🙂

No errors.

Output is like this:

Something<tab>something<tab>something

Not:

something,something,something

Here's the sqlcmd command, produces tab delimited data rather than comma.

declare @sql varchar(8000)

set @sql= 'SQLCMD.EXE -d SynDocsDB -i D:\MSSQL\SSIS\export.sql -o \\csg-cold01\cold\ABD\export'+ @datesql+ '.csv -s"," -W '

print...

Cool. I agree, no need to re-invent anything.

So this should suffice for the csv export?

xp_cmdshell "select col1,col2,col3 from table" -oc:\myfile.csv -h-1 -s",

Thx for the reply.

So, something like this, but using xp_cmdshell? 'sqlcmd -q "select col1,col2,col3 from table" -oc:\myfile.csv -h-1 -s","'

What about a retention period of these files? I guess I need...

Our own backup job was doing the same thing...

I will keep digging too on my end. Thanks for your help.

I did all that, including the DCOM local group. What's even stranger is that the AD group I am part of is local admin on this server. I'm missing something...

It's just an access denied error. "Connecting to the Integration Services service on this computer "servernamecensored" failed with the following error: Access is denied."

No cluster, and I'm trying to connect locally.

Do I need to configure something in the SQL Server Configuration Manager?

Still getting access denied, and yes I restarted services.

Any way to do it without creating roles?

HowardW (9/11/2012)

---

Yikes, lots of data there - could you edit that and remove all but the top couple of hundred rows or so as it's going to be very slow...

Results:

database_namephysical_device_nameBackup_SizeCompressed_Backup_SizeUncompressed_Throughput_MB/sCompressed_Throughput_MB/sElapsed_Backup_Time_Minutesbackup_start_daterecovery_model

PRDU:\PRD_Backup\PRD1.bak4421 GB781 GB187334022012-09-10 18:20:13.000FULL

PRDU:\PRD_Backup\PRD2.bak4421 GB781 GB187334022012-09-10 18:20:13.000FULL

PRDU:\PRD_Backup\PRD3.bak4421 GB781 GB187334022012-09-10 18:20:13.000FULL

PRDU:\PRD_Backup\PRD4.bak4421 GB781 GB187334022012-09-10 18:20:13.000FULL

PRDU:\PRD_Backup\PRD5.bak4421 GB781 GB187334022012-09-10 18:20:13.000FULL

PRDU:\PRD_Backup\PRD6.bak4421 GB781 GB187334022012-09-10 18:20:13.000FULL

PRDU:\PRD_Backup\PRD1.bak4411 GB777 GB189333972012-09-09 18:20:10.000FULL

PRDU:\PRD_Backup\PRD2.bak4411 GB777 GB189333972012-09-09 18:20:10.000FULL

PRDU:\PRD_Backup\PRD3.bak4411 GB777 GB189333972012-09-09 18:20:10.000FULL

PRDU:\PRD_Backup\PRD4.bak4411 GB777 GB189333972012-09-09...

Has the database size increased? Check the backup sizes from the msdb backup history tables over a few weeks to see if there's been a significant increase

--> No dramatic increase....