The command will stop the execution of the operation and will be followed by a rollback which can take a long time - depending on the size of the data...

Books Online:

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/fe20dca9-a4c1-4d32-813d-42f1782dfdd3.htm

Look at full-text search in Books Online. You can create full-text indexes on textual data (stored in [var]char, [var]binary or XML columns).

Yes, there is, but it will require sending user credentials (login name and password) to the server. That's why using integrated (Windows NT) security is the preferred option.

Either way, you'd...

How are you connecting to the remote server - are you using the same account that you used to create the database?

Are you sure you're connecting to the right server?

You haven't given us any details. We can guess, but I'm pretty sure you don't want that. 🙂

What component are you trying to invoke? Is it installed on the server?

Does...

Look up sql:column and sql:variable in Books Online.

For a more accurate answer, please, provide a sample query (including table DDL and sample data) and a sample of the XML.

What exactly would you like to see in the joined result set?

You need a way to correlate the result sets returned by all the queries.

Please, provide an example of the...

Almost. If there's a view of the same name in the current database then the local view will be used.

Try this:

-- Create view in tempdb

usetempdb

go

create viewdbo.sp_theview

as

selectgetdate() as Today

go

-- Create view...

That could work. With limitations. 😀

SQL-DMO is deprecated as of SQL Server 2005. The new library is SQL Server Management Objects (SMO) - look it up in Books Online (e.g.: http://msdn2.microsoft.com/en-us/library/ms162169.aspx).

No, you cannot make a view a system object (as you can with procedures). You can create the view in the master database, but you'd still have to reference it...

You have to grant the SQL Server service account appropriate permissions in the folder on your local machine and use the UNC name in the query.

E.g. (untested):

Assuming the UNC share...

Google "parameter sniffing".

And next time, post the procedure definition so that we don't have to guess what the problem might be.

> 1. would this affect performance?

No. It shouldn't.

> 2. Is this good practice to change it in the database level? or should just put it in each sp?

For the database-wide...