If you are feeling adventurous and want to turn on CLR within your SQL instance, the procedure at the sqlteam weblogs is very nice and will give you information about...

Hey Ism,

There is no "performance" penalty for using mount points and you should definitely still use three separate LUN's for each mount point. There is however a flexibility issue...

Very interesting indeed. It does appear however that SQL Server 2005 will implicitly "convert" your varchar to an int without you specifically casting it (I'm not sure if...

This blog post from the PSS (Product Support Services) team does a great job (in my opinion) at "un-muddying" (is that a word?) the SP2/GDR water.

http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx

IMHO, the .NET domination will continue once the UNIX/Linux shops start taking a serious look at Novell's Mono. No longer is .NET relegate to just Windows platforms (at least...

No problem.

Thanks for the log post. I am not sure if this will help or not, but there maybe another process that is logging onto your SQL Server prior...

Sounds like the service pack installer is having problems connecting to the instance via shared memory. The service pack attempts to connect via shared memory and places the sql...

Just my .02 ....

If you do have an active/active cluster, then it might be a good idea (as Steve suggested) to set your max memory configuration to 5 GB for...

Agreed.

Try explicitly re-adding the system account back to SQL Server. Something like:

use master

EXEC sp_grantlogin [NT Authority\System]

EXEC sp_addsrvrolemember [NT Authority\System] , 'sysadmin'

go

should work.

I agree with the previous post. Make sure that your proxy account has the Bypass Traverse Checking right. Also, we have had to make sure that our proxy...

If you are a glutton for punishment, you could implement IPSec between your SQL Servers (not just the AH - Authentication Header stuff ...).

Or set up something like a secure...

Since you are using the "out-of-the-box" LogShipping facility, check out this whitepaper:

http://support.microsoft.com/default.aspx?scid=kb;en-us;323135&sd=tech

But to answer your question, it is not really difficult to restore the "primary to standby" log...

If Terminal services/RDP is not feasible, another possible VPN like approach would be to get an SSH server installed on the "shared" SQL Server (like Vshell, or Cygwin with SSH,...

Very interesting .. we had a similar problem when our servers were migrated to AD ... and reconfiguring the SQL Server Agent worked for our situation. Check out this...

Either add an Active Directory Domain account to be the SQL Server Agent service account, or change your DTS scheduled jobs to run as a SQL Login account (i.e. sa...