This seems to work for managing 'legacy' SSIS packages through 2012 SSMS:

http://www.ssistalk.com/2012/03/21/connecting-to-a-pre-sql-2012-ssis-instance-with-sql-2012-ssms/[/url]

In case this is use to anyone else: I've had some problems with running legacy packages after upgrades....

Just to say - I finally got the chance to do a completely vanilla upgrade from SQL 2008 R2 and again ended up with 2 IS services. 🙂

That's helpful to know, thank you. In my case, I also found that I was getting errors around VSTA, and couldn't upgrade or run any packages on from within...

I think it's very unlikely that anyone else will have this problem but just in case! What seems to have happened is that SSIS was installed as 'eval', rather...

Great article - very helpful!!!

It's two-phase commit, but if the mirror is unavailable, the transactions will still be committed as far as the principal is concerned, they'll just be queued in the transaction log,...

I've seen this issue before, we ended up having to work around it. The closest I got to an explanation was this: http://support.microsoft.com/kb/912151, may not apply...

Test that you can failover and then take the principal server completely offline as well. I realise that this shouldn't make any difference but have seen a case where...

Useful article - scary but useful! I didn't realise this was possible.

Also works on SQL 2008 R2 by the way...

Try db_backupoperator on each database. You'll need to add the user to the dbcreator role at the server level if you want the user to be able to verify...

You can see the ansi settings by querying sys.dm_exec_sessions.

Ok then, if you absolutely have to do it as an in-place upgrade, I'd recommend that you have a look at Allan Hirt's book - Pro SQL Server 2008 Failover...

When you use a local variable, SQL has to estimate the selectivity of the 'where' clause, because it doesn't know the value of the variable when it optimizes the query....

There are 4 quorum modes in Windows 2008 - 3 of these involve 'node majority', which means each node in the cluster has a vote. In 'node and disk...

If you're prepared to move away from maintenance plans, you could write a custom log backup job that only backs up the logs for databases that aren't being log shipped...