Tag Info

New answers tagged

3

OLEDB via ADO has always had the issue where DONE_IN_PROC messages (rows affected) confuse code that is not expecting them. A workaround without app code changes is to specify SET NOCOUNT ON as the first statement in the batch: SET NOCOUNT ON; DECLARE @s varchar(1000), @ver int; SET @ver = 10; SELECT @s = case WHEN @ver > 9 THEN 'BACKUP DATABASE [DB] TO ...


2

A1. How large are the databases? If you need logical backup, you can use mysqldump (--single-transaction, --master-data are some options you need to review and use). For speed, you want to go with mydumper/myloader tool. It will also make sure of taking individual dumps. Advantage here is you can grab the database you need to restore without having ...


2

While copying a tablespace, it automatically includes data files and indexes associated with it. You need to make sure that tablespace is self contained. Confirm that tablespace is self contained execute DBMS_TTS.TRANSPORT_SET_CHECK('<TABLESPACENAME>', true); Use the TRANSPORT_SET_VIOLATIONS view to check if any violations condition exists select * ...


0

I think just -- exporting db and taking out the json file and import in another system. Or You can directly copy the db from one location to another---- http://docs.mongodb.org/manual/reference/method/db.copyDatabase/


6

Rather than saving your procedures in user tables, why don't you just set up a SSDT database project and use version control (TFS, Git, Mercurial, SVN or whatever you find appropriate) to take care of versioning? SSDT or other tools such as Red Gate's SQL Source Control will help you in keeping track of versions and deploying your changes to your ...


2

You can use sys.sql_modules (MSDN): select top 10 * from sys.sql_modules as m inner join sys.procedures as p on m.object_id = p.object_id where p.name ... It is better to alter them because you won't have to worry about existing permissions. If you drop and create the procedure, you have to set them back. DO: if not exists, create empty dummy SP and ...


1

Use pg_restore to list its contents, dump it to SQL, or restore it to a database.


1

You can't download a snapshot from RDS you have to use a tool like pg_dump This has already been answered multiple times on regular Stack Overflow: http://stackoverflow.com/questions/14916899/download-rds-snapshot


2

Please then modify your database to be in 'SIMPLE' recovery mode instead of 'FULL' or 'BULK LOGGED'. The full recovery mode never truncates the transaction log, unless you do a transaction log backup. Only after it's backed up will SQL Server reuse the empty space in the transaction log. Now setting the DB to simple mode, taking a full backup, and ...


2

You're restoring with pg_restore --format=c ... but the pg_dump was not done with --format=c, it was done with the default, plain format. From pg_dump manpage: -F format, --format=format Selects the format of the output. format can be one of the following: p, plain Output a plain-text SQL script file (the default). ...


1

RMAN uses backupsets by default. The following commands will create a backup to a backupset: RMAN> backup database; RMAN> backup database plus archivelog; This is assuming that you haven't changed the default RMAN parameters: RMAN> SHOW ALL; ... CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP ...


1

I've found that full backups are not supported on the secondary replica just read only backups. A full backup has to be performed on Primary replica. That will serve a base for the diff or T-log backups. A COPY_ONLY backup is supported on secondary replica. You can do transaction log backups on either primary or secondary databases. Check my answer - ...


1

I suppose that you looked at the Oracle site (http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmquick.htm)? If not then look here: http://www.thegeekstuff.com/2013/08/oracle-rman-backup/.


2

The method you describe is ok. This method was the backup method used before Oracle introduced RMAN and is still valid. It is still used by tools that do snapshot backups (like Netapp's backup tool for Oracle) and I often use this in similar situations. You also should make a controlfile backup if all the controlfiles are on these disks.


1

If you can create a snapshot of everything at the same time, you do not even need backup mode. Backup mode (User Managed Backup) is not deprecated, but RMAN is the preferred tool for making backups.


1

I would do a shutdown of the database to be sure that really nothing is written on the filesystem of the SAN. Do you have your archivelogs on the same filesystem? Restart it after you have made the snapshot. The alter database begin backup; is in the 11g documentation so it must be still valid (have not checked it for 12c). Do you make full backups with ...


10

Yes. Details here: Backup Overview (SQL Server) This is the section relevant for you: Full backup A full backup contains all the data in a specific database or set of filegroups or files, and also enough log to allow for recovering that data. You should always test the backup (ideally by performing a restore to another location) to ensure you can ...


0

Given only the single server for production. Since you didn't mention a dev environment. If I were me, I'd run an export of the warehouse1 structure. No data to go with it. Then I'd invest some time to generate testdata. They don't need to be live data. They'd have to represent usecases. Given the structure and testdata, I'd have everything I need for ...


1

I don't think you can verify an SSAS database isn't corrupt apart from querying it. If you query it and you get errors it's corrupt. If your database ends up corrupt the only sure way to recover is to restore the last known good backup, even though sometimes you can get away with messing in the .xml files or the data folder structure there is no guarantee ...


1

I think Ops Manager (can be deployed as local MMS) fits your requirement: … Ops Manager assists with: Deployment. Any topology, at any scale Management. Deploy new clusters. Manage, monitor, and back up existing ones Upgrades. In minutes, with no downtime Scaling. Add capacity, without taking the application offline Point-in-time, ...


3

MongoDB doesn't have an automatic backup feature built-in -- you have to choose an appropriate backup strategy using command-line or third party tools. The backup procedure will vary depending on your deployment type (standalone, replica set, sharded cluster), disk/dbpath configuration, and backup requirements. Unless you are using a third party tool, ...



Top 50 recent answers are included