It is difficult to answer the question, because I don't know why you set up different schema owners in the first place. My preference is to have dbo to own...

You can also capture them with SQL Trace. Note that...

I guess it will give some clue, but maybe not enough, unless these logs are large. A better test may be the restore of the full database backups. A few...

Let me first commend you for adding that primary key. That constraint served as an assertion of your assumption about the data. Your assumption proved to be incorrect, but thanks...

When you have a syntax error, you need to read the query in tokens. You have:

exec master.sys.xp_cmdshell BCP "SELECT FileContent FROM

[StoreReferenceFiles] WHERE FileId = '1F4CA617-2296-482E-B909-24B69B83EDAA'" queryout "\\spicity605\Pricelist\docs_test.xlsx" -T-n

That is

EXEC <identifier>...

The thing about "one file per core" is not correct, but what is correct is more difficult to say. I vaguely recall something about 1 file for every four cores,...

So your problem is really about how to get DTC to work. And that is not trivial if the conditions are not the rights ones. In a domain with trust...

Let me ask you one thing: if the call to dbo.sp_send_dbmail, or for that matter anything else in the trigger, fails, do you want the statement that fired the trigger...

kevinsql7 (9/9/2013)

---

to assign permissions ... not sure why I had to do this. Do you know? With TestUser1 as the schema owner, it returns the following error:

"Cannot grant, deny, or...

Are these logins Windows logins or SQL logins?

When your login fails, what do you see in the error log? There should be the same error message as you get when...

Note sure what you actually did; the CREATE TABLE statement should pass. It would be easier to make dbo owner of the schema from the start, but it does not...

On SQL 2008, you can use the command SET FMTONLY ON:

SET FMTONLY ON

go

--you query goes here

go

SET FMTONLY OFF

although, this is quite an ugly hack and it will not work in...

When you get this error, this either because the value is a duplicate in the source data, or because your query produces duplicate rows because of an incorrect join condition...

Certainly a bit of a mystery!

I can explain the part about the trailing space: if you save a value with trailing spaces in a varchar column, the trailing spaces, provided...

If you add YD.Framework and YD.Level to the result set, what values do you see in these columns?