SQL Server 2005 Best Practices Analyzer (January 2008) -- Now Available!

Noticias externas — Sat, 19 Jan 2008 01:08:54 GMT

It's a new year and, with it, we come bearing gifts! We have a pretty significant update to SQL Server

re: SQL Server 2005 Best Practices Analyzer (January 2008) -- Now Available!

Imran — Thu, 24 Jan 2008 17:25:59 GMT

The BPA is not able to connect to a remote server or a Named instance on the local server. Is this by design?

re: SQL Server 2005 Best Practices Analyzer (January 2008) -- Now Available!

Paul Mestemaker — Tue, 29 Jan 2008 04:20:38 GMT

Imran and I are discussing offline. SQL Server 2005 BPA can only connect to SQL Server 2000 and 2005 based servers. It cannot connec to SQL Server 2008. If anybody else has issues with BPA, please submit a question to http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=84&SiteID=1.

-Paul

re: SQL Server 2005 Best Practices Analyzer (January 2008) -- Now Available!

esmith1844 — Wed, 20 Feb 2008 20:02:38 GMT

In running the SQL 2005 BPA (Jan/08) I am getting a critical error.. Outdated system Driver that can cause paging detected - SQL Server Processes are Paged Out.. I have followed the directions updating the server BIOS, network card firmware and driver to the latest as well as the OS - TCPIS.SYS also identified in the issue description. I have also tried disabling the TCP Chimney Offload.. to no avail as I still get the 17890 error in the Application log of the server. The server is an HP DL 360 - G5, 32GB of RAM, W2K3 server x64, the server network cards are HP NC373i, SQL Server 2005 SP2 + Cumulative Updates to 3175.. .

Even with the latest of all of the above results in the same error 17890 - 'A significant part of sql server process memory has been paged out...' at start up.. any suggestions???

What do I do now??? Any suggestions?

re: SQL Server 2005 Best Practices Analyzer (January 2008) -- Now Available!

Andre1602 — Fri, 29 Feb 2008 08:59:06 GMT

esmith1844 I have the exact same issue on a HP DL580 G5. Did you find a solution?

re: SQL Server 2005 Best Practices Analyzer (January 2008) -- Now Available!

PaulB — Mon, 14 Apr 2008 19:12:18 GMT

We are also seeing error 17890 in our environment, any suggestions?

re: SQL Server 2005 Best Practices Analyzer (January 2008) -- Now Available!

NM — Thu, 15 May 2008 17:10:58 GMT

Ditto, did anyone find a solution?

re: SQL Server 2005 Best Practices Analyzer (January 2008) -- Now Available!

SQLMan — Wed, 21 May 2008 00:27:17 GMT

Having the exact same issue with a Dell 2950. Any ideas anyone?

re: SQL Server 2005 Best Practices Analyzer (January 2008) -- Now Available!

Fran — Mon, 02 Jun 2008 18:04:20 GMT

I'm trying to run SQL 2005 BPA 2008 against a SQL 2000 server but get the following error:

Dcom got error "<error description>" from the computer <computer name> when attempting to activate the server: <server component>8BC3F05E-D86B-11D0-A075-00C04FB68820

Has anyone had this problem?

Additional Info:

The server is running Windows NT 5.0 (Build 2195: Service Pack 4)

The SQL Server version is Microsoft SQL Server 2000 - 8.00.2039

re: SQL Server 2005 Best Practices Analyzer (January 2008) -- Now Available!

Paul Mestemaker — Wed, 04 Jun 2008 22:25:55 GMT

For the 17890 errors... take a look in your event log to see when the last time it happened (Event ID 17890 in the Application event log). Let's say it happened on Feb 1... you ran BPA on Feb 8... corrected the issue on Feb 15. BPA will continue to detect the old entries in the event log. If you do not see any new errors after Feb 15, you are ok.

-Paul

re: SQL Server 2005 Best Practices Analyzer (January 2008) -- Now Available!

Rob — Mon, 11 Aug 2008 14:50:22 GMT

Suggestion for the next release (SQL2008) - allow end user to set a specific date to scan back to. It has been extremely frustrating to correct an issue only to have it show up again in new scans. So, if I fixed all the issues a month ago and I want to see only what the new issues are, I set that date as the starting point. Selecting "Do not this issue again..." is not enough because I want to know if the same issue crops back up.

re: SQL Server 2005 Best Practices Analyzer (January 2008) -- Now Available!

cool4now — Tue, 26 Aug 2008 21:13:32 GMT

Running the upgraded BPA on the same servers I ran the previous version on, I am now getting the Outdated system driver at [C:\WINDOWS\system32\ntoskrnl.exe] error with file version 5.2.3790.4035. How could the latest SP have an outdated system drivers? I am getting this on 2003 x86 32-bit R2 Enterprise with SQL Server 2005 Enterprise and 2003 x86 32-bit R2 Standard with SQL 2005 Developer, both O/S running w/SP2 and SQL 2005 SP2. Is this a bug?

re: SQL Server 2005 Best Practices Analyzer (January 2008) -- Now Available!

Rob — Fri, 05 Sep 2008 16:42:04 GMT

Is it possible to completely clear all results of scans and basically reset SQLBPA to the point when it was first installed? Issues I have corrected continue to appear even though i believe I have corrected them. I don't want to ignore the issue because I want to be sure I actually corrected the problem. Uninstalling and reinstalling does not seem to clear out results. Deleting all the repost files also does not clear the results. Where are the results stored?

re: SQL Server 2005 Best Practices Analyzer (January 2008) -- Now Available!

Don Cavin — Thu, 11 Sep 2008 00:32:59 GMT

1) Can you clear out your event logs to avoid the situation of seeing old (but corrected errors)?

2) Is there some ability to extend the bpa, to setup your own rules, etc.? That would be helpful...something similar to the Oracle Enterprise Manager where you could write your own tcl code to define your own threshold and rules relative to your specific information?

Thanks,

Don Cavin

xwave