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
Trying to run the following :
ALTER DATABASE mssqlsystemresource
MODIFY FILE (NAME = data, FILENAME = 'D:\MSSQLSERVER\MY_SQL_SERVER_INSTANCE\Data\mssqlsystemresource.mdf')
GO
ALTER DATABASE mssqlsystemresource
MODIFY FILE (NAME = log, FILENAME = 'D:\MSSQLSERVER\MY_SQL_SERVER_INSTANCE\Data\mssqlsystemresource.ldf')
GO
error is :
Could not locate entry in sysdatabases for database 'mssqlsystemresource'
Tried the following and it solved the problem:
NET START MY_SQL_SERVER_INSTANCE /f /T3608
The "/f" switch - This flag starts SQL Server with minimal configuration and allows updates to system tables. Sometimes a DBA makes config
changes , which won't allow the SQL Server instance to start.The switch is useful , as sometimes it is the only way to correct
configuration mistakes
The "/T3608" flag skips automatic recovery for all databases except the master database at the startup
Source:Jack Vamvas (http://www.sqlserver-dba.com)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: |