Be extremely cautious using repair_allow_data_loss. There is zero guarantee that it will fix the problem by dropping one or two pages worth of data. It can, in some cases, nuke...

SequelDBA (4/27/2015)

---

I have a SQL 2014 Express instance that a developer installed. Currently, we do not "officially" support SQL 2014. I want to move the 2014 database to a 2012...

It's a memory error. It could be pretty benign, just a momentary read/write error in memory that's not going to repeat. It could also be corrupt pages in one of...

If the transaction log is growing a lot, two things. One, take more frequent log backups. That will free up the committed transactions more often. Two, maybe you just need...

I'd go with the latest service pack, yes.

I'm not sure this will address any performance issues you're hitting. This may or may not be related. I would capture wait statistics,...

You need to look to what the execution plan is telling you for how it's going to resolve this query. Your indexes are not being used or the statistics are...

Here's the documentation on CREATE PROCEDURE. That will get you started in putting your query into a procedure. Then, as Jeff said, it's a question of calling it using the...

It's most likely a data problem within the cursor itself. I'd focus on what that cursor is doing specifically within the code in order to understand where the problem might...

Just call it right within the procedure as stated. Here's the documentation.

Have you looked at the execution plan for the query? That will tell you why it's running slow.

You can include this information in the connection strings from the application and then it will be available in SQL Server. But, if it's not a part of the connection...

Service Broker is a messaging and queuing engine within SQL Server. You can read more about it in the Books Online. It appears that this error was addressed by a...

In that case I'd just pull them directly from source and publish them that way. PowerShell will be fully automatable, you can connect to multiple servers, and with threading you...

I'd suggest writing a PowerShell script to run the export and import of the procedures. That should be fully automated and ought to work well.

Another approach would be to put...

I think your logic is sound. I'm just a big fan of testing things to be sure.