Search
Subscribe
Categories
- Backup and Restore
- Capacity Planning
- Compression
- Configure
- Contact me
- CPU
- Data Architecture
- Data Import and Export
- Database Mirroring
- DBA
- DBA Scripts
- DBCC
- Deadlocks
- Default Trace
- Development
- Disaster Recovery
- Disk Storage
- DMV
- Documentation
- Event Log
- Execution Plan
- Function
- High Availability
- Indexes
- Install & Setup
- Interviews
- IO Subsystem
- Isolation levels
- Jobs
- Latches
- Links
- Locking
- Memory
- Monitor Performance
- MS DTC
- MSDB
- Network
- Object Management
- Pagination
- Partitioning
- Performance
- Powershell
- Security Management
- SQL Agent
- SQL Azure
- SQL Blocking
- SQL Cachestore
- SQL DAC
- SQL Default Trace
- SQL DTS
- SQL Error Logs
- SQL Execution Plan
- SQL Optimizer
- SQL problems
- SQL Query Tuning
- SQL Server Error Tips
- SQL Server Management Studio
- SQL Server Profiler
- SQL Server Tuning
- SQL Trigger
- SQL View
- SQLServer-DBA News
- SSIS
- Statistics
- Stored Procedure
- T-SQL
- TempDB
- Tools
- TPC-H
- Transaction Logs
- View
- Virtualization
- Wait Stats
SQLServer-DBA.com Links
Recent Posts
- Task Manager not showing correct SQL Server memory usage
- The value of training and How to convince your boss
- SQL Error 1204 - cannot obtain a LOCK resource at this time
- Multi-statement table valued function and inefficient Excecution Plan
- SQL Server Export to Excel with Powershell
- Who dropped the table in SQL Server
- List sql database roles
- SQL Execution Plan - Comparing Estimated Rows and Actual Rows
- DCOM got error "Logon failure: unknown user name or bad password” Event 1004
- SQL Server Triggers and Performance
02 February,2013 by Jack Vamvas
Justifying a SQL Server version upgrade is easy from a technical perspective. Justifying a an upgrade from a business perspective is more difficult. As a DBA , you need to convince the business of the upgrade value. Keeping up to date with SQL Server version support levels is one tactic to convince business of the upgrade value
A SQL Server upgrade involves costs such as – infrastructure, licensing costs for SQL Server and supporting software such as monitoring agents and skills training for support staff. One method to assist the DBA is to detail the support levels on SQL Server.
The current support level status for SQL Server 2000 and SQL Server 2005 is :
SQL Server 2000 – Extended support will finish on April 19th,2013. This includes no more software updates and security updates
SQL Server 2005 – Extended support started on April 12th ,2011. Security update support remains without any extra cost. Non security hotfixes require an Extended Support Agreement.
Depending on the organisation and the standards they maintain , these dates are important and have cost implications for support. Depending on the application criticality using a product which is completely out of support or has limited support can have cost and reputation implications.
Read More
SQL Server – How to Ask for support and troubleshoot problems
AWE SQL Server memory not supported in future releases
Author: Jack Vamvas (http://www.sqlserver-dba.com)
Verify your Comment
Previewing your Comment
This is only a preview. Your comment has not yet been posted.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Posted by: |