Right. So instead of using the OS to store your path, put it into a config file and map the SSIS package to read the config file to get...

Why would you do that? Couldn't the data from the system variable be transferred into the config file? IMO depending upon the OS for that sort of thing...

The SELECT @variable = SCOPE_IDENTITY needs to be the very next statement after the insert to ensure you are getting the proper IDENTITY. So before the END.

No. Do your insert as normal without reference to the ID column. The insert will create the row and generate the identity. The very next statement after...

So I assume then that you are using Basic Authentication with the user name and password? If you use Windows Auth it WILL use the SQL Server service account.

Can't...

OK, you are not making any sense to me. You say "same account" and "different account" in the same breath, you say that the setup on this server is...

Plus there are DR scenarios for which log shipping is perfect, far more suited than mirroring. I think it would be a mistake to remove the feature.

Sounds like the SQL Server service account has write-only access to the directory, and can't read from it. Check to make sure that read access is available in both...

But that would also deny the DB he needs, though, right?

Are you sure that the mail account is set up in the mail server correctly? You're getting a mailbox access error; if this were Exchange, I would assume that...

This is an edited job creation script to show what I mean.

USE [msdb]

GO

DECLARE @FileName NVARCHAR(200)

DECLARE @FilePath NVARCHAR(200)

DECLARE @ConfigFile NVARCHAR(200)

SELECT @FilePath = 'C:\'

SELECT @FileName = @FilePath + 'test.dtsx'

SELECT @ConfigFile = @FilePath...

timscronin (7/27/2010)

---

It is the same account my other 2008 and 2005 servers use, the difference is I used this exact account for the service accounts for sql server on myohter...

Looks like an Exchange setup issue. Are you sure that the account being used for DB Mail has an Exchange mailbox created? You can't do anything without that...

For a GROUP BY query, you can only order by columns in the SELECT list. Therefore the only way to do what you need is to put the month...

Because of the support issues that Gail refers to, we find that it is a waste of time to monitor SQL Servers running SharePoint. Best to make them reside...