Perhaps the apostrophes in the data is monkeying with something? And is it the datetime field -200 that is causing the integer error?

Grant Fritchey (2/5/2014)

---

TheSQLGuru (2/5/2014)

---

Grant Fritchey (2/5/2014)

---

But the FAST (50) hint is also going to impact what gets delivered by the optimizer. It's likely to see what you're seeing, a seek...

I would not be surprised at all to see inconsistent and/or buggy handling of NULL "character" in a string. I would file a Connect item if you feel it...

Grant Fritchey (2/5/2014)

---

But the FAST (50) hint is also going to impact what gets delivered by the optimizer. It's likely to see what you're seeing, a seek where a scan...

JoseM (2/4/2014)

---

Recently I received the task to build an AlwaysOn Setup with more than 5000 databases in four SQL Server instances . Customer wants to use their current hardware that...

lots of things you can specify with a plan guide and if they get picked they get used as is AFAIK.

Please Private Message me when you make your new thread, I don't want to miss it! Thanks!

You need to look at the DETAILs of your query plan to see what is happening here. Put your cursor over the seek operator in the graphical query plan...

jvazquezm (2/4/2014)

---

Hi gurus !!

Check if you have any error in the SQL Server Errologs related with avaliable workers and raise the value in case you find this error.

How many...

New to SQL Server doesn't mean you can't format your code to be readable. Same for the output. ...

I would forget the single user stuff. Indexes may well be best if dropped and recreated when you are updating 15-20% of all rows. It isn't cut and...

greg.bull (2/4/2014)

---

Thanks all. Strikes me this isn't very good. I think it's the same for update and delete too. I guess it's complex/very difficult to chunk up the work and...

I said to put the OPTION (RECOMPILE) INSIDE the sproc attached to the SELECT statement. What you had here was likely a form of parameter sniffing where the first...

your data and query are so poorly formatted I can't make heads or tails out of either. I do note that you are using non-ANSI joins (bad move -...

The estimated rows being way off is either getting you a big table scan and hash join which is killing your time and possibly opening you to blocking too, OR...