Hi Experts,Wondering to know how to handle this situation.I would like to address performance issues in production so I would want to make some table(s) as in memory residing table(s). So that entire data from the disk based table stored in memory and be easily accessible to application. We got enough memory in production server so we dont have any issue with some table(s) as they are having few billion rows. We do use redgate SQL server db backups scheduled in production server so they do take incremental back up every 2 hours and at the end of day full back ups.I used to copy the full back up file to my development server and restore that in development server for further fixes or enhancements. Until now its working fine as all are disk based table though they have billions of rows.Now my doubt is.As I am in a plan to make some table(s) as memory residing table So wondering how it works when redgate sql server back up. My assumption is it back up with the same configuration as it is. If so once I try to restore that in development server again my assumption is it fails. As my development server does not have that much memory to keep entire table with billions of rows. I am sure it fails to restore.Did any one of you experienced or encountered this situation?So how to handle this issue?Help me out.Appreciate in advance.
↧