Dave D's questions

I'm trying to set up a copy of the CodeCollaborator trail software for performing code reviews but when I try and point it to our SVN repository I get the error

Error: Invalid input: Version control server configuration error: Could not create valid Subversion configuration based on configured repository url: svn: OPTIONS of 'https://svnserver:8443/svn/Repository': Server certificate verification failed: issuer is not trusted (https://svnserver:8443)

However, I've no idea which certificate to grab or where to install it. I've tried running a simple svn list https://svnserver:8443/svn/Repository/ which gives me the error

Error validating server certificate for 'https://svnserver:8443/svn/Repository/:

• The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually!

Certificate information:

• Hostname: svnserver.domain.local
• Valid: from Tue, 12 Aug 2008 10:27:29 GMT until Fri, 10 Aug 2018 10:27:29 GMT
• Issuer: svnserver.marvel.local
• Fingerprint: (set of hex values) (R)eject, accept (t)emporarily or accept (p)ermanently?

Thereafter I can run svn commands at the commandline without a problem, but still get the error setting up CodeCollaborator.

What certificates do I need to install, and where, to get this up and running?

I have three maintenance plans set up to run on an Sql Server 2005 instance:

• Weekly database optimisations followed by a full backup
• Daily differential backup
• Hourly transaction log backups

The hourly log backups are usually between a few hundred Kb and 10Mb depending on the level of activity, daily differentials usually grow to around 250Mb by the end of the week, and the weekly backup is about 3.5Gb.

The problem I have is that the optimisations before the full backup seem to be causing the next transaction log backup to grow to over 2x the size of the full backup, in this case 8Gb, before returning to normal.

Other than BACKUP LOG <DatabaseName> WITH TRUNCATE_ONLY, is there any way to reduce the size of that log backup, or prevent the optimisations from being recorded in the transaction log at all, as surely they will be accounted for in the full backup they precede?