I have servers in a merge scenario that replicate every ten minutes. When
changes occur, they need to replicate fairly quickly (within 30 minutes),
but changes may not occur in every hour.
I think it would be most efficient to run continuous rather than every 10
minutes. However, I would really like replication to not be running at all
outside of the 8am-5pm window. Is it possible to have continuous
replication, but only from 8am to 5pm? The SQL Enterprise Manager does not
seem to allow for it.
Rob Kraft
Sure. Add a job that runs at 8AM and again at 5PM. What does this job do?
It changes the schedule on the replication job.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
sql
Showing posts with label occur. Show all posts
Showing posts with label occur. Show all posts
Wednesday, March 28, 2012
Monday, March 19, 2012
Is it possible to audit Failed Insert, Update and Delete statements?
Auditors want us to track when Insert, Update and Delete failures occur. Is this possible in SQL 2000?
They also want us to track schema changes. Is this possible?
Thanks, DaveWhat constitutes a "failure" for the purpose of the audit?
-PatP|||The statement does not execute and returns an error. I believe I can trap this failures in Profiler, but I'm not sure what type of overhead this would create. Several people have suggested triggers, but I'm not sure a trigger will execute on failed attempts, only successfull insert, updates and deletes.
If I take the Profiler approach I'm not sure it will show schema changes.
Dave|||If you tell it to, SQL Profiler can track ANYTHING that goes to SQL Server. DML that works or fails, schema changes, and everything else. The question is: How much disk are you willing to dedicate to making this happen?
With the Profiler running "wide open" on a moderately busy server you are looking at 2-3 Tb of data in a 24 hour period... Once you've collected the data, you need to figure out what (if anything) you are going to do with it!
The old Chinese adage applies: Be careful what you wish for, you might get it!
-PatP|||We will only be monitoring two or three ids. Not sure if a domain group can be monitored, but if so we will monitor at the group level. This is for Sarbanes-Oxley complaince, which is basically very strict management of database systems for financial institutions. My thanks to Enron. Our DBAs are allowed to manage development and model office environments and a consulting company gets to manage production. Sarbanes-Oxley requires we keep an eye on the production DBAs by monitoring their activity. Profiler may not be the best approach. Even though we will be monitoring a small number of ids, SQL Server still needs to perform conditional logic against all user activity to see if the filter criteria is being met. A software tool may produce less overhead.
Thanks, Dave|||Everybody loves the joy of SOX!
If you really, really need to, you can get C2 (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_config_09yd.asp) auditing from SQL-2000. There are thousands of auditing combinations, many of which are pretty much designed for exactly what you want to do.
I'd be hard pressed to recommend a third party product for this use... At least in my opinion, it is likely to be more work than it is worth in the long run.
-PatP
They also want us to track schema changes. Is this possible?
Thanks, DaveWhat constitutes a "failure" for the purpose of the audit?
-PatP|||The statement does not execute and returns an error. I believe I can trap this failures in Profiler, but I'm not sure what type of overhead this would create. Several people have suggested triggers, but I'm not sure a trigger will execute on failed attempts, only successfull insert, updates and deletes.
If I take the Profiler approach I'm not sure it will show schema changes.
Dave|||If you tell it to, SQL Profiler can track ANYTHING that goes to SQL Server. DML that works or fails, schema changes, and everything else. The question is: How much disk are you willing to dedicate to making this happen?
With the Profiler running "wide open" on a moderately busy server you are looking at 2-3 Tb of data in a 24 hour period... Once you've collected the data, you need to figure out what (if anything) you are going to do with it!
The old Chinese adage applies: Be careful what you wish for, you might get it!
-PatP|||We will only be monitoring two or three ids. Not sure if a domain group can be monitored, but if so we will monitor at the group level. This is for Sarbanes-Oxley complaince, which is basically very strict management of database systems for financial institutions. My thanks to Enron. Our DBAs are allowed to manage development and model office environments and a consulting company gets to manage production. Sarbanes-Oxley requires we keep an eye on the production DBAs by monitoring their activity. Profiler may not be the best approach. Even though we will be monitoring a small number of ids, SQL Server still needs to perform conditional logic against all user activity to see if the filter criteria is being met. A software tool may produce less overhead.
Thanks, Dave|||Everybody loves the joy of SOX!
If you really, really need to, you can get C2 (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_config_09yd.asp) auditing from SQL-2000. There are thousands of auditing combinations, many of which are pretty much designed for exactly what you want to do.
I'd be hard pressed to recommend a third party product for this use... At least in my opinion, it is likely to be more work than it is worth in the long run.
-PatP
Subscribe to:
Posts (Atom)