By: Jeremy Kadlec | Comments | Related: > SQL Server Configurations
Problem
When it comes time to review server related information from your SQL Server be sure to know how and where to access the information. With SQL Server 2005 some of the resources have changed and new resources have popped up. This tip outlines core server related information from SQL Server 2000 to 2005.
Solution
Mapping server information between SQL Server 2000 and 2005 is critical to ensure scripts are working properly when upgrading to SQL Server 2005. Below outlines the common server related objects.
| ID | Information | SQL Server 2000 | SQL Server 2005 |
| 1 | System table\view with all server related information for the local, remote and linked servers | SELECT * FROM master.dbo.sysservers GO |
SELECT * FROM master.sys.servers; GO |
| 2 | General SQL Server metrics for 1 server | sp_helpserver 'ProdSQL1' GO |
sp_helpserver 'ProdSQL1'; |
| 3 | Listing of the server wide configurations | sp_configure GO |
EXEC sp_configure; |
| 4 | Configures server options for remote or linked servers | sp_serveroption 'ProdSQL1', 'collation compatible', TRUE GO |
sp_serveroption 'ProdSQL1', 'collation compatible', TRUE; |
| 5 | System function returning server information such as the collation, edition, instance name, security configuration, etc. for the SQL Server | SELECT SERVERPROPERTY('Edition') GO |
SELECT SERVERPROPERTY('Edition'); |
| 6 | Approximately 30 connection related parameters primarily for ODBC | EXEC sp_server_info GO |
EXEC sp_server_info; |
| 7 | Function to return the SQL Server instance name | SELECT @@SERVERNAME GO |
SELECT @@SERVERNAME; |
| 8 | System stored procedure to return the sort order and character set for the SQL Server | sp_helpsort GO |
EXEC sp_helpsort; |
| 9 | Listing of the active processes | sp_who2 active GO |
EXEC sp_who2 active; |
| 10 | System table\view with real time system processes in SQL Server whether the process (spid) is active, sleeping, etc. | SELECT * FROM master.dbo.sysprocesses GO |
SELECT * FROM sys.dm_exec_sessions; GO SELECT * FROM sys.dm_exec_connections; GO |
Next Steps
- As you begin to learn SQL Server 2005, make the switch from using the old objects to the new objects to ensure you are not spending time with depreciated code sets.
- If some of these commands are new to you, start to test them out and keep them in the back of your mind as future needs arise.
- Check out these related MSSQLTips:
- Stay tuned for future tips mapping the system objects between SQL Server 2000 and 2005.
About the author
Jeremy Kadlec is a Co-Founder, Editor and Author at MSSQLTips.com with more than 300 contributions. He is also the CTO @ Edgewood Solutions and a six-time SQL Server MVP. Jeremy brings 20+ years of SQL Server DBA and Developer experience to the community after earning a bachelor's degree from SSU and master's from UMBC.This author pledges the content of this article is based on professional experience and not AI generated.
View all my tips
