Search
Subscribe
Categories
- Backup and Restore
- Configure
- Contact me
- CPU
- Data Architecture
- Data Import and Export
- Database Mirroring
- DBA
- DBA Scripts
- Deadlocks
- Development
- Disaster Recovery
- Disk Storage
- DMV
- Documentation
- Event Log
- Function
- High Availability
- Indexes
- Install & Setup
- Interviews
- IO Subsystem
- Jobs
- Links
- Locking
- Memory
- Monitor Performance
- MSDB
- Network
- Object Management
- Pagination
- Partitioning
- Performance
- Powershell
- Security Management
- SQL Agent
- SQL Azure
- SQL Cachestore
- SQL Error Logs
- SQL Optimizer
- SQL problems
- SQL Server Error Tips
- SQL Server Management Studio
- SQL Server Profiler
- SQL Server Tuning
- SQL View
- SQLServer-DBA News
- SSIS
- Statistics
- T-SQL
- TempDB
- Tools
- TPC-H
- Transaction Logs
- Virtualization
- Wait Stats
Recent Posts
- How to check Operating System type with Powershell
- ALTER TRACE and developers
- Predict ALTER INDEX REORGANIZE finish time
- Cannot connect to SQL Server
- Timeout occurred while waiting for latch: class 'LOG_MANAGER'
- The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time
- How to create a SQL Server Security Audit
- Cannot use Large Page Extensions: lock memory privilege was not granted
- Compare two files with Powershell
- Export-CSV Powershell
These are some basics when it comes to development on SQL Server.
Insufficient change control testing -Potentially the worst mistake to make, where developers will use a test case. Do a full TPC benchmark.
Unrealistic test environments - Provide an adequate db for the developers. One easy way is to export the production statistics into the test db
No change control procedure - In busy software companies, version control for schemas and sql code is paramount
Not enough testing instances- Thorough SQL developers often keep 4 environments, DEV for development, TEST for unit testing, QA for pre-production testing, and PROD for production. Any less and you risk missing errors
No performance tracking - With all the counters and alerts handling , there's no excuse for missing early warning signs, not to mention custom software packages
Poor security management - SQL Server offers a host of access control mechanisms. In dbs I audit, I still see obvious security holes
Non-standard external environments - This is a bad practice where every database uses different versions, inconsistent aliases and non-standard/varying file locations.
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: |