February 4, 2014 at 10:01 am
I have received this message on two different activities. The first time was when trying to move one table to a file group on a separate array with CREATE CLUSTERED INDEX in a Management Studio window. I posted it in one of the Microsoft Forums and got no solution to this issue. I ended up using another server to successfully test that script. Both servers are SQL 2012 Standard Edition 64 bit and both were updated in place from SQL 2005 SE 64 bit. But today I got the same error on the first server while trying to execute in Management Studio a restore that works on a scheduled job. There is no dump, no entry in events beyond Management Studio losing connection and the server is not affected. The very same statement that failed this way in SSMS is now running fine in a scheduled job. What both types of script have in common is only that they are long running scripts that run for several hours.
I would appreciate any information that I can get on this subject. My research has not turned up anything related.
Thanks in advance,
Eduardo
February 4, 2014 at 12:58 pm
Try this thread. http://www.sqlservercentral.com/Forums/Topic1163878-391-1.aspx
You might also try searching the exact topic of your post. It returns a number of hits.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
February 4, 2014 at 1:03 pm
Thanks but I have already run DBCC CHECKDB and there were no errors found.
February 5, 2014 at 3:30 am
One thing I thought I should add, both servers, the one having this issues and the other one where the processes worked, received recently a new array to accomodate the moving of some tables to the secondary filegroup. Hardware diagnostics run on both of them did not detect any problem.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply