Thanks for the post! I just verified the server name is correct and matches the server name in the error message.

Although installing the IBM Client was my solution, I still had to figure out the correct parameters to return the objects I needed like the previous install. With IBM...

Sure, I am glad you liked the idea!

Hi Sean, The new version is better than ever!

I have made a change that I thought would be helpful to me and possibly others as well so I thought I...

Joes ErrorLogReporting code uses SP xp_readerrorlog. If you cycle your SQL Server error log daily be sure to schedule your report BEFORE you cycle your error log because the...

FYI, For me to get Joes ErrorLogReporting section incorporated and compiled on 2005 I had to change the 2 declare statements to be:

DECLARE @vTodaysDate VARCHAR(20); set @vTodaysDate = CONVERT(VARCHAR(20), GETDATE(),100)

DECLARE...

Can I please get the full guide from you. Thanks!

Thanks Lee, I didn't even think about that! Now I dont have to modify my version when Sean posts a new update. 😉

Sean,

Thanks for a great article! I, too, made a tweak that might be useful to others? I created a parameter "flag" that I can pass to skip the...

Thanks Gail, I was looking under delete a database and it said nothing about it.

I found this out on SQL Server 2008 R2 and confirmed on 2005 too.

Thanks for the responses! So from what I am gathering, its better to consider adding more disk space to allow for the incresed size of the log files than...

Thanks, Again!

Is this something I should be configuring every time I do a SQL Server install of one instance?

My apologies! You were correct. I am still learning how to use the Configuration Manager!

I was looking at the wrong TCP/IP protocol. I saw port 1433...