(DT_STR,4,1252)YEAR(entry_dt) + "-" + RIGHT('00' + (DT_STR,2,1252)MONTH(entry_dt),2) + "-" + RIGHT('00' + (DT_STR,2,1252)DAY(entry_dt),2) + "-" + (DT_STR,4,1252)job_no

If you turn on logging, you will be able to see which object ends up with a buffer overflow.

It is possible that writing to the oracle server is taking too...

Or if you need this in just one procedure, there is an OUTPUT clause that will allow you to return the inserted or updated records into a table variable.

Assuming the table has a date field indicating when each row was added and rows cannot be deleted, it meets Inmon's definition just fine.

In both definitions, the final format of...

I don't understand your question.

Perhaps you could post some sample data and an example of what you want.

If you are looking for a single sum, you need to do the case inside the aggregate:

select trans_Date,'MD' as org,

--case when rate_cat = 'INTER'then sum(trans_amt)*0.1 when rate_sub_cat='IR'

--then sum(trans_amt)*0.1 else...

Package configurations will allow you to configure one package for multiple sources.

Using one job per client in the Job Agent would also allow you to simply specify the connection strings...

Along with questions, people post DDL and sample data in usable formats in that universe as well.

So there are some benefits.

There you have it.

If you have faith in your users, it is ok to turn it on.

...and if a flying pig stops by...

But remember that it is not just preventing locking, it is also able to potentially read the same record multiple times, skip records that are in the table, and read...

The *32 means the process is running on WOW. So, what you are seeing confirms that your server is running the 64 bit operating system as it should be....

I honestly cannot remember. I do remember that MS decided to disable it by default way back between sp3 and sp4 on SQL 2000.

I think you would need to...

I'm pretty glad as well.

The alternate universe in which two files could be in the same folder with the same name would be a very confusing place to live.

Also, are you aware that the NOLOCK query hint can cause miss-reads, duplicate-reads, and reading of uncommitted data? This query hint is very often misused and misunderstood.

Look up "Cross Database Ownership Chaining".

You may want to consider creating some views of the small amount of data they can get to in the second database and giving them...