Hi folks,

I was hoping I could get someone from the esteemed Elevate community to weigh in on the specifics of the read lock behaviour when performing backups using DBSYS. All references to the backup functionality that I have seen indicate that the backup "obtains a read lock for the entire database". However in DBSYS, one can limit the scope of the backup by selecting only the specific table(s) that one wants. My question therefore is: will the read locks be placed only on the selected tables, or will all tables in the database be locked irrespective of whether they were selected or not?

Best Regards,

Jason  

If you select a subset of tables the only those selected will be locked.

It's also a read lock so other apps can continue to read data from those
tables during backup.

Raul


On 7/18/2012 4:49 PM, Jason Wilson wrote:
> Hi folks,
>
> I was hoping I could get someone from the esteemed Elevate community to weigh in on the specifics of the read lock behaviour when performing backups using DBSYS. All references to the backup functionality that I have seen indicate that the backup "obtains a read lock for the entire database". However in DBSYS, one can limit the scope of the backup by selecting only the specific table(s) that one wants. My question therefore is: will the read locks be placed only on the selected tables, or will all tables in the database be locked irrespective of whether they were selected or not?
>
> Best Regards,
>
> Jason
>

<<
If you select a subset of tables the only those selected will be locked.
>>

Correction - entire DB is actually read locked not just selected tables.

Raul