I have written a stored procedure that executes an SSIS package in my SQL Server 2012 database. The SSIS package loads data from a file into a table when executed. If there is data in the table, it deletes the existing data and then writes the new data to the table. This was a great solution when only one user was using the stored procedure. Now more users are using this feature, and could possibly use it simultaneously. I need to somehow lock the execution of the stored procedure, if another user is in the middle of running it. How can I do this? Do I need to add syntax in my stored procedure that would prevent this from happening?
Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline
In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied?
You can use SQL Server Initialize from Backup…