I have a query where the optimizer does not choose any parallelism in the execution plan which runs in about 45 seconds.

then I put the option (maxdop 1) hint in...

this will actually create schema locks on the remote server and the local server, since it has no stats on the remote table, will request various table/column stats to be...

Redgate software

SELECT  IDENTITY(int, 1, 1) AS RowNum, CustomerID into #tmpA from northwind.dbo.orders

select * from #tmpA

that only seemed to do it.  if you have text > 8k you will get truncation.

Look in BOL for UPDATETEXT which will handle what you're actually asking for.

Check to see if the database is marked for publication for replication.  If so, then you might have transactions in the log marked for replication which have not been picked...

try putting it in a stored procedure with a parameter on the remote server.

then invoke it from your local server.  should run on the remote and return only what you...

Which build of sp4 are you running?  The initial release of sp4 had some big problems.  If you're on anything less than 2187 you should patchup.    I've seen this as...

I think the only granularity you can get is at the file level.  There is a function ... fn_virtualfilestats ??? ... something a along those lines which will tell you...

try starting up sqlserver from the command line.  it should start up as the oldname.  once you start it up, you'll probably need to drop the old server .... sp_dropserver...

the only system table is msdb..sysdtspackages.  however it's binary format.

there is a vbscript out there which will interate through that table and save the packages as structured stored files or...

I tried your error number and took the db offline via sp_dboption.  I didn't get alerted.

I also tried 942 and then tried use dbname ... go in QA and see...

"balk data will be inserts per 3 months"...

I'm still trying to understand the question... are you concerned with bulk insert performance?

bcp and the BULK INSERT command are very fast.  Try...

If you're shrinking a large file, I would run dbcc updateusage first.  Then start shrinking the database in small increments.  You might find that your shrink fails if you specify...

some more info...

from sql-server-performance.com

http://www.sql-server-performance.com/reducing_locks.asp

One way to help reduce locking issues is to identify those transactions that are taking a long time to run. The longer they take...