Sql-server – Monitor Sql Server 2000

sql serversql-server-2000tools

I was wondering if there is a free tool to monitor state of SQL Server 2000. I would prefer a web tool.

I would like to see if some database is accessible, or are there any problems on server, etc. Also I would like not to put to much extra load on SQL Server.

If anybody knows tool like this, please help

Thanks

Best Answer

The Zabbix tool, posted in the comment, is not really working, because the server doesn't run on Windows, only the agent. See info in their requirements page. This means you'd need to install the tool on a Linux machine and only an agent on the Windows machine. Great if you have a heterogeneous environment, not really helpful in a full Win environment.

The same situation is for Nagios, another interesting open source monitoring tool. They say there is a package only for Windows, but the doc page it redirects to doesn't work now.

Of complete free monitoring tools useful for SQL 2000 I'm not really aware, but you can use successfully a pair of:

Perfmon (find more info here)
Server trace (trace specific queries, not just everything) -> actually files that can be open in SQL Profiler
SQL Alerts (info in MSDN article or here, in this SimpleTalk article)

PS: found that a great monitoring tool is also working on SQL 2000. So you'd better try to test Confio Ignite free. It's fantastic for the price :-).

PS2: there is also a small free monitoring tool from Idera -> SQL Check, but I don't know if it works on SQL 2000.

Related Solutions

Sql-server – Changing SQL Server 2000 usernames

Some notes

When you create a login, then the name must match AD exactly
EXEC sp_grantlogin 'DOMAIN\Andy Soell
When you map the login to a database user, it can be renamed
EXEC sp_grantdbaccess 'DOMAIN\Andy Soell', 'Dilbert'

The 2nd bit will fix your issue with implied schema. This happens if don't qualify schema (eg dbo) because SQL Server 2000 has pretty much no user-schema separation like later versions

Note: you can't rename users in SQL Server 2000 IIRC: need to run sp_revokedbaccess then sp_grantdbaccess. If you own objects because of your implied schema then you'll need sp_changeobjectowner. I think SQL EM will prompt you.

That is, you should always qualify schema in SQL Server.

CREATE TABLE dbo.viewname...

SELECT * FROM dbo.myTable

EXEC dbo.MyProc

Then no need to change the users

Sql-server – SQL Server 2000 to SQL Server 2008 linked server issue

I've had this problem before, and while I didn't find a fix (as it appears from the error message, SQL Server seems to 'lose' the brackets when it's processing the query), I did find a couple of workarounds:

Using OPENQUERY will allow you to use the linked server name as-is.
(My preferred solution): create a synonym for the linked server and use that in your query:

CREATE SYNONYM MyLinkedTable FOR [DBNAME.DATABASE.ORGANIZATION.COM].DBName.schema.TableName

Then use it in place of that huge mess:

SELECT * FROM MyLinkedTable

Best Answer

Related Solutions

Sql-server – Changing SQL Server 2000 usernames

Sql-server – SQL Server 2000 to SQL Server 2008 linked server issue

Related Question