Tag Info

Hot answers tagged

15

A database may contain malicious code, possibly a procedure that is going to change a password for the "sa" login or drop every database. However the only way that I can see that causing an issue is for an individual to restore the database, and then manually execute any code within that database. It would not execute in any automated manner. There is no ...


10

There are some prevention steps that you could do. Make sure no one but one sysadmin has access to the restored database. Put the db in single user mode after the restore is completed. Check the code inside all stored procedures and functions and triggers inside this database. Perform a dbcc checkdb to make sure there are no integrity issues. Check ...


8

I'm reaching here, but I can think of at least one dangerous scenario: if you restore a database that has a filetable, those files are now on your network by default (and specifically, on your SQL Server). You could restore a virus. That by itself won't do anything, of course - the virus doesn't suddenly become sentient - but if your users then try to ...


6

The question focuses mostly on a backup containing malware, but it's also possible to get unwanted and potentially malicious behaviour from the restore operation itself. I've accidentally found in the past that it's possible to crash SQL Server by trying to restore a corrupt backup file that causes SQL Server to try to read past the end of the backup file ...


6

There are multiple ways to get to the intended target recovery point with your setup. A few things: You cannot eliminate log backups for the most important reason of transaction log re-use. It's not possible to know when an issue will occur and thus having multiple ways to get to the RPO is useful and sometimes necessary. Differentials aren't a substitute ...


6

RESTORE VERIFYONLY would seem to be a good first step. The ultimate answer is probably 'restore the database in a sandbox VM with no access to the outside world', but let's assume that option is off the table. What else should be done in this situation? Restore verifyonly verifies integrity of database it WILL NOT tell you whether backup includesa ...


4

What risk is there is restoring an unknown database from an unknown source? None. What risk is there in letting an unknown application connect using a sysadmin account to connect to that database and start running code? LOTS! If the application account only has rights within the database and no server level access then there's nothing it can really do ...


3

There are lot of things I would like to say What I'm looking for is some suggestions or 'gotchas' that may arise from switching some to the FULL recovery model. As far as I know if you change recovery model of database during maintenance window time or when load is relatively less there wont be any problem. It wont create a situation. I'm also ...


2

We want to handle schema changes Transactional Replication would be hard to maintain. If you do frequent schema changes, then you have to drop replication and recreate it, which is time consuming and on the top of it, you have to maintain distribution database as well. Network latency also plays a big role if you are replicating your entire database. ...


2

You're issuing a "recover database" command, which will recover the database as far as possible. If that includes the archivelogs/redo logs which contain your "truncate" command, then this will also be re-played and the table truncated again. Try doing the restore on it's own, or recovering to a specific time using RECOVER UNTIL... then opening the DB ...


2

Given what you ask I would say pg_dump is not the tool you want. You want to do hot copy with point in time recovery which will allow you to take the database back to any specific point in time will all the config files in one place. Here is what you do, check the configuration you must have enough wal kept for this to work, so if the backup starts at 1am ...


2

I will answer you question point wise like you asked No its not necessary that LSN of differential backup would match the LSN of full backup. LSN is basically a stamp of last records that accessed the log. You should have also included DatabaseBackupLSN/checkpointLSN and then you will note that DatabasebackupLSN of differential backup will match the ...


1

Depending on how up-to-date, you want the reports to be, you can use Log shipping : with delay of log restore on secondary and choosing the secondary to be read only with disconnect users when restoring the log. This will allow you to have read from secondary server. you just have to balance between the restore frequency on the secondary. log shipping ...


1

There are not alot of dangers per say, other than some far-reaching ones suggested here. As was mentionned, it is hard to have auto-executing stuff in a database backup itself. It needs some kind of exterior triggerring mechanism. Get an old laptop/desktop and an evaluation version of your Database software (SQLExpress) if licensing is an issue. Copy the ...


1

You're handed a database backup and told to restore it to a server (that's already hosting other databases), but are given no useful information about what the backup contains or whether the source should be trusted. Nice. You demand a signed written statement from whoever is telling you to do this that they accept full responsibility for the ...


1

Generally speaking a differential works very similarly to a full backup, except that only the changed extents in the DCM are backed up. Differential backups still contain a portion of the log needed to be transactionally consistent. This will differ for every environment and is not "known" at the time of backup. You can use the RESTORE HEADERONLY of the ...


1

Does this mean I will need to do a full backup on primary if a restore of the transaction log is required? NO -- You can add t-log backups to a restore of a COPY_ONLY backup


1

Note the blog referenced in the answer given by @Gyre will not work for creating an "application" read-only user (i.e, for creating a read only role for a web application to connect to the database), and might open up a serious security vulnerability, since its easily circumventable, as explained in this postgresql list response. For reference, by the client ...


1

Yes, this scenario is possible in NOCATALOG mode. I did exactly this on 9.2 last Saturday so I can vouch for it :) Your attempt was almost successful. The only thing you did wrong is you restored the control file that was too new, it was above Reset SCN 246779908. If you move away C:\brubru\auto\c-2176828955-20130518-00 it would probably find a bit older ...



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