Tag Info

New answers tagged

8

Does the backup process USE only the memory that Has been assigned to the sql server (instance)? The memory that you assign with MIN and MAX memory is just for Buffer Pool and for SQL Server 2012 and up, the memory manager has changed. When a backup starts it creates a series of buffers, allocated from the memory outside the buffer pool. The ...


0

Free Space BACKUP DATABASE (full backup, differential backup, file/filegroup backup, copy only) does not free up space in any files. If anything, it uses up a bit of space in the log file to record its actions. BACKUP LOG truncates the log, which generally does free up space. A Simple recovery model database truncates its log when a checkpoint happens. ...


1

Got a SQL database and the log file is massive and keeps growing every day. Log files growth depends on Recovery Model of a database and transaction log backups. if database is not critical and data loss is not an issue in any case then it should be in SIMPLE recovery mode. Which allows SQL Server to reuse log space when a transaction is committed and ...


3

You have corrupted your database by manually deleting files from within the data directory. Never delete files from within the data directory manually. Safely removing WAL If you want to remove WAL, either let the server do it at CHECKPOINT time, or use pg_archivecleanup. Note that the server will remove WAL is no longer needs automatically, unless: ...


0

Looks to be a post-completion check failure as there is no evidence elsewhere stating otherwise.


0

Seems like a good reason to visit the Oracle Documentation site. The 2-day dba documents are very good. If your database is running in ARCHIVELOG mode, it copies all transactions to the archivelog destination. The transactions are always written to the redolog files but when they are full, they are only saved when running in archivelog mode. This enables ...


1

There is no way to grant backup but restrict to certain options. Stop giving them permissions to backup databases. Create a stored procedure that executes as owner and backs up the database with copy_only, and give these users exec rights on the stored procedure. If you need this for multiple databases you can create multiple procedures or you can use ...


3

You could create a simple audit report which shows who is doing the non-COPY_ONLY backups, eg select user_name, min(backup_start_date) min_backup_start_date, max(backup_start_date) max_backup_start_date, count(*) records from msdb.dbo.backupset where is_copy_only = 0 group by user_name


3

No there is no option or restriction which we can enforce so that a user can take copy_only backup when ever he tries to take any backup but what you can do is create a procedure which backups database with copy only option and grant execute on the procedure to various users and then remove backup database privilege from the user. BACKUP DATABASE and BACKUP ...



Top 50 recent answers are included