Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
 Posted - 2003-11-27 : 02:53:46
|
| A bug has been discovered with the undocumented DBCC PSS command that can cause SQL Server access violations in certain circumstances (this affects all versions of SQL Server 7.0 through SQL Server 2000 SP3). This command is used by the Microsoft Best Practices Analyzer, the SQL Server 7.0 and 2000 blocking detection scripts (as documented in KB articles 251004 and 271509), and the PSSDIAG utility (documented in KB article 830232). This is not an issue with these tools, per se, but rather with the DBCC PSS command itself.Until a fix is released that addresses the DBCC PSS issue, Microsoft recommends that you do not use this command on production SQL Server instances. The use of the command has already been removed from the tools mentioned above. If you are using the Microsoft Best Practices Analyzer, please download the latest version immediately. If you are using the blocking detection script for SQL Server 7.0 or 2000, please obtain the latest version of the blocking detection KB article (251004 or 271509, respectively) and replace the version of the script you are currently using with the one contained in the article. If you are using the PSSDIAG utility, please contact PSS to obtain a version of the tool that does not call DBCC PSS. |
|
|
|
|
|
FYI: DBCC PSS can cause access violations