Hot answers tagged

11

No, this is not possible.SQL Server 2017 backups cannot be restored by any earlier version of SQL Server ref Also, regarding detatching and reattaching per the docs: After being attached to SQL Server 2017, the database is available immediately and is automatically upgraded. This prevents the database from being used with an older version of the ...


7

Well, reading the documentation for Resource Database (highlighting mine) The Resource database is a read-only database that contains all the system objects that are included with SQL Server. SQL Server system objects, such as sys.objects, are physically persisted in the Resource database, but they logically appear in the sys schema of every ...


2

In addition to what Scott said about the Resource DB — [mssqlsystemresource] — that it's read-only (which is entirely correct; it's SQL Server application data), it needs to be stated that no database "contains information on all objects in its server instance". That concept does not exist in SQL Server: not for [mssqlsystemresource], nor [master]...


1

The Log file of database is fragmented too much and there are too many Virtual Log Files. This would force recovery to take longer time. Run dbcc loginfo(db_name) on database and tell me how many rows it returns. Please see How a Log file Can affect database restore time The SQL Server service account does not have "Perform Volume Maintenance Task" privilege ...


1

As long as you state that you did restore before and it took much less time I would quess that some of the following could be the reason: some other process on the reporting server taking a lot of resources (in- and outside of SQL Server), that put high load on disks; slow network connection between backups and reporting server if backups are located on a ...


Only top voted, non community-wiki answers of a minimum length are eligible