Kind of crab sold to your boss.

You should indeed disable them if you are not using sql agent jobs.

If your system is secure and you have implemented all security related...

Probably you're using DHCP addresses on your client.

The IPadress registered is the one it had at install time.

It's the port number that is unique for your machine, so that's the...

We've has some connection losses to, but the mirroring (primary-mirror-witness) resumed as soon as the connection could be reactivated between principal and mirror.

It caught up very well (sql2005 std)

I know...

did someone enable tcp/ip access for your instance ?

If not, this should be done (using sqlserver configuration manager followed by a stop/re-start of your sqlserver instance)

Keep in mind : many...

I always love to see alternatives ....

But going back to use the unstable sp_oa... is at least one bridge to far.

There has been a nice article with a CLR...

Regarding the FK indexes: http://www.sqlservercentral.com/scripts/Indexing/61391/

For the rest all I can say is: "With quick only comes dirty !!"

Capture your workload, and analyse it (maybe using Db Engine tuning advisor)

Only...

for your cluster, off course the backup location will be the same (for drives will fail over or UNC drives are the same)

If I'm correct these registry keys are replicated...

IMO MS did build a great product with wanted technology, but lost the battle before it had begun because of the lack of managebility aids !

Just considering you may have...

I always suggest to support all FK with indexes, unless proven they hurt a specific case. Then only remove/disable (but document ! ) the hurting one if that case occurs...

How about this:

-- Alter Local Default Backup Directory and check existance / create if needed

--

Declare @NewDrive nchar(1)

Declare @RootDirectory2Add nvarchar(512)

Declare @NewDirectoryPath nvarchar(512)

Declare @Override char(1)

select @NewDrive = N'K'

, @RootDirectory2Add = ''

...

check out the free SQL Server Migration Assistant for Access (SSMA for Access)

http://www.microsoft.com/sqlserver/2005/en/us/migration-access.aspx

It will point you to some issues and the way to fix them.

Off course, it will only...

also have a look at the auto grow size. Maybe someone set it way to big.

also nice to read: http://sqlblog.com/blogs/aaron_bertrand/archive/2009/10/16/bad-habits-to-kick-mishandling-date-range-queries.aspx

indeed, the order of execution of the log truncation _after_ the diff backup causes the log to be unusefull for recovery purposes.

Maybe a log analyser tool can still recover...

afaik you nolonger need the assembly once you have created it in sqlserver.

You can even script it. That will generate a long binary string, but will be portable.

So you can...