Check the sql server service.

If it's using local system account, it won't work.

You need to start the service using a 'normal' windows account.

Then grant this account permissions on the...

Since you are already concatenating, you could do something like this...

create view myView

as

SELECT col1 + char(13) + char(10) + col2

FROM myTable

GO

/Kenneth

Not quite sure what you mean by a 'slice'...

But from the example, my guess is that you want a value if it exists in all three tables, otherwise not?

You can...

Sometimes dirty reads can prove to be helpful, though one needs to be aware that it's not entirely without risks.

There is a (perhaps remote, but nevertheless) risk, that a dirty...

It also works should you dare dabble with dynamic SQL.

use tempdb

go

declare @sql varchar(255)

set @sql = 'use master select db_name()'

exec ( @sql)

go

/Kenneth

Another take on part1:

insert newTable (application)

select application1 from tab1 union

select application2 from tab1 union

.....

select application8 from tab1

Repeat for through tab5, or if there may be dupes in tabs 1-5, union...

What's wrong with select db_name() ..?

/Kenneth

It's the magic that makes our days interesting

/Kenneth

The third variant of expressing the same thing as the shown LEFT JOIN and NOT IN is to use a NOT EXISTS construct.

/Kenneth

Can you post some sample rows of data and table structures that demonstrates the problem you're having?

/Kenneth

Post the DDL of the tables you have, and some sample rows of data.

Then we have someting to work with, and maybe something can be done.

/Kenneth

You should also consider to change the datatype to a datetime, then all 'number to date problems' goes away.

If you have data that is a date, it should be treated...

Yup... Forgot to mention that

/Kenneth

Another idea instead of messing with remote proc calls of a user proc, could be to set up a job that execs the restore on MSDB4.. Then you could just...

It's not uncommon that a view works fine, but when you stack views on top of each other, you may get poorer performance than when using those views separately.

It's one...