New answers tagged

1

Docker images tagged with latest contain the latest release at the time you retrieve it (this is Docker's convention), thus the image in the source contains different TimescaleDB's version (1.6.0) than in the current latest image (2.1.0 is latest now). This leads into the error of missing binary, since the images are not the same and the current latest image ...


1

If you are just looking for nomenclature to name the process, I would call it DB Sandbox Provisioning DB Self-Service Provisioning DB Self-Service If you need an actual process supplied by Amazon, you could look into AWS Control Tower AWS Service Catalog If you are planning to script this yourself, there is always the AWS CLI. create-db-snapshot restore-...


0

You can generate the scripts from SSMS and include the data. See this. This is what I would do if I needed a one time move of the schema and the data.


3

You generally do not do it. It is not possible. SQL Server is not forward compatible. 2017 does not know how to handle a 2019 backup. PERIOD - no discussion, it will tell you so. Which is why it is an utterly stupid idea no to use the same versions over the whole application development team cycle - you make copy operations complex, you run into ...


4

A backup is overkill for only one table and I'm not sure what compatibility issues you can run into restoring to a lower version of SQL Server (since backups occur at the database level). Instead you should look to just copy the data between servers. There are a multitude of ways and tools out there to help you do this, but I've always found the SQL Examiner ...


0

If you create the backup using the --tts option, when restoring your instance you can include/exclude selected tables. A whole database is included/excluded by selecting all of its tables with --include/exclude="^databasename\." The MySQL official documentation explains it very well: TLR: https://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/...


5

There is no single right answer to a vague question like this, and the interviewer isn't expecting one (if they know anything themselves of course). They are looking to test how you realise the question is too vague and how you might start trying to answer such a question in a real situation - to see if you understand what extra details would be needed and ...


11

These kind of questions are stupid interview questions in my opinion, and definitely need more context. Perhaps they just want to see your thinking and what follow up questions you'd ask for clarity. If by processed they mean 650 MB of data is added every month (and even here would be an assumption that the added 650 MB is data + all indexes + any other ...


13

This is an open-ended interview question that doesn't have a precise answer. The interviewer might expect you to ask additional questions for clarity. Actual space requirements will depend on what is meant by "processed" (inserted?), data retention (are data ever deleted?), column data types, indexes, storage overhead, use of compression features (...


1

As has already been posted by David Browne - Microsoft, I would like to expand on the concept I was using in my answer form the comemnt. If you have a database, you can use the WITH STANDBY... feature and have the database restore to a certain point-in-time (your last TLOG backup) and then have the database in Standby / Read-Only mode. The steps you wold ...


3

I would like to run a process that loads in the latest log file every hour and then run a full restore once a week (when we receive the latest bak file). Is there anyway of doing this? Assuming you run the same version of SQL Server, Yes. What you're looking for is called RESTORE WITH STANDBY: RESTORE WITH STANDBY Leaves the database in a standby state, ...


0

Your first output is showing as EWKT (Extended Well Known Text) while the second output is WKB (Well Known Binary). These are both standard representations of the internal geometry but are designed for different end users (human v machine). To be honest I have never see PostGIS return WKT in a standard select statement, usually you would wrap the geometry in ...


0

Turned out this was just lack of memory on the chosen RDS instance. Increased it to the "medium" instance instead of "micro" and it imported fine at around 10x the speed, with all tables.


6

The two managed types of SQL Server in Azure (SQL Database and Managed Instance) are version 12.0.2000.8. Don't be fooled by the low version number, it is always higher than on-prem meaning you can never restore an "Azure SQL" backup to on-prem. You cannot perform a backup from SQL Database, but you can do a copy only backup from Managed Instance. ...


3

Would it be possible to mount additional drives on the target SQL server, restore the data files to the new drives and then simply change the location of the data files in the DB once the restore is complete? Yes, if the two databases on the target server have the same file layout. A simpler and safer procedure is to restore the database with a different ...


0

... I restored database 'A' in DEV server with it's production copy ... You now have Production data in a non-Production environment, an eventuality that may or may not be covered by your organisation's Privacy Notice and, therefore, may or may not place your company in breach of GDPR (or similar) legislation. You might want to think about that. However, ...


1

The following commands export data without mixing it with role or privilege data so that you can import it to any role you specify. Also, you can make pg_dump compress the data to a tar file for you. pg_dump --format=t --blobs --verbose --no-privileges --no-owner \ --password --username mydbuser --database mydbname \ --file "mydbname_dump_$(date +%Y%m%...


0

The error might be a bit misleading. It is correct to restore the control file from the latest backups assuming you want to recover to as late in time as possible. If your control_file_record_keep_time is long enough to also contain the backup pieces of the level 0 backup, rman will start restoring the level 0 backup and continue with the level 1 backup. If ...


0

Yes, you can move your base directory to any location you wish where the postgres service has write access and enough storage available. There are a few things to note your startup script needs to set it's PGDATA directory correctly to the new location your clients that connect locally have to set their PGDATA to the new location. Tablespaces in postgres ...


Top 50 recent answers are included