
Do you use ROWVERSION/TIMESTAMP to pull changed data? If you do, you might experience a problem – not all changed rows are pulled, some are skipped. How can that be, if we pulled entire range of rowverion changes with no…
Databases should be fast and simple to use. We make them so. Do not let your customers wait for a slow database response - hire a top professional! We are passionate about creating highly-tuned SQL Server systems. Do you want yours to become one? Simply call us or send email, and we will take care of the rest.
Vedran Kesegić, M.Sc.
SQL Server Database Consultant
Email: vedran.kesegic@gmail.com
Keep your transaction log backups at least to second full backup. Even if the latest full backup is corrupt, you can recover without any data loss. E.g. if you take full backup weekly, diff backup daily, and transaction log backup hourly, keep your transaction log backup at least for 2 weeks, so it reaches the second full backup.