Have you got a covering index for this query ? Is this index also partitionned ?

However, it's a lot of data, it will take some time.

And don't forget to give execution permissions if needed.

Float and real are approximate data types. Therefore you should use decimal.

Select all your jobs, right click, All tasks, generate sql scripts. It's pretty straightforward. 🙂

http://msdn.microsoft.com/en-us/library/aa177024(SQL.80).aspx

Far far far away from being a genius, thanks 😛

Anytime. 😛

Sean Lange (10/17/2013)

---

Yes you need the case expression in your group by. You also should really consider using aliases in your queries. It would make this a lot more legible....

Indeed. Thanks 🙂

I think you need to repeat the case statement in your group by clause.

SELECT [WorkForce_WorkOrder].[Work Order ID_WO]

--,[WorkForce_WorkOrder].[GHRMS Contingent Worker ID_WO]

,[contractor ID] = CASE

WHEN [WorkForce_WorkOrder].[GHRMS Contingent Worker ID_WO] is null

THEN...

Anytime 🙂

SELECT DATEADD(s, -1, DATEADD(m, DATEDIFF(m, 0, GETDATE())+1, 0))

Check this post. Might help.

http://carlosbercero.com/post/?post=Writing_a_CLR_Stored_Procedure_on_SQL_Server

Use master..xp_cmdshell or CLR stored procedures instead.

master.dbo.xp_dirtree is an undocumented and unsupported procedure.

Steve-0 (10/17/2013)

---

Ok just a bit of digging and it looks like the failover is the way to go:

http://technet.microsoft.com/en-us/library/ms186348(v=sql.105).aspx

My question at this point is, how does this affect any...

Have you got a witness configured ?

You would need to fail over to the mirrored database in order to make this one as principal i think.