doh!

:blush:

Thanks for the info Gail (or dbinfo) 🙂

there is also the version column in master.sys.sysdatabases. Interestingly though MSDN (from 2008 onwards) says 'Not supported. Future compatibility is not guaranteed.'

wonder why.

its R2? oops, apologies.

sounds like their version is in fact SQL2008, so you need a 2008 instance as well

not enough information to help there. Is there a stack trace in your SQL log directory or any further messages in the errorlog.

As a fatal exception this might require MS...

the copy and restore jobs run on time schedules but are driven by 'what was the last log I copied\restored from logshipping directory so which is the next one...

please see http://msdn.microsoft.com/en-us/library/ms189292.aspx, the third answer is incorrect, I am sure Steve will rectify the situation.

this actually follows on from the question two days ago, which is why I answered...

logshipping creates a SQLAgent job to backup the log. So set the alert to execute that job. The job itself can be disabled so it doesn't run to a timed...

yes it does.

All the page moving that reindexing does is recorded in the log so is therefore replayed on the secondary database.

Just the same as if you restored a database...

another option is you can set up an alert in SQLAgent on log threshold. Set the log size at 100mb and get the alert to fire off the log backup...

Any stack traces in your log directory?

the longest part of a cluster failover is usually recovering the database(s). Check the time of the first message in the errorlog and the...

SQL 2008 SP1 CU1 (10.0.2710)

when the instructions say right click select 'new,' new is not an option, and then connect, connect is not an option

specifically these instructions seem inaccurate

http://msdn.microsoft.com/en-us/library/bb934126(v=SQL.100).aspx

last thing you want to do is get developers excited, they can be pesky little critters then....:-)

Also, remember 2008 ---> R2 is not the same as say 2005 ---> 2008. R2 is much more 2008 with extras.

Hence why the versions for SQL2008 are 10.0.nnnn and for...

Marios, we are running SQL2008 R2 RTM and on a pretty meaty machine. We have had no issues.

I would only apply a CU if you are hitting an issue it...