sudhakara (7/28/2010)

---

jezza101 (7/28/2010)

---

You might find the answer...

Good question and use of the undocumented sp_MSforeachdb.

Now, I have a remark here, the question stated "...disable all triggers in a database".

As Hrvoje noted above, Database scoped triggers as well...

Great question.... something new learned 🙂

As Lowell mentioned, it makes no difference if you use different users when they touch the same tables.

I would actually look at the underlying code that causes the blocking. In...

Performance will definitively not be an issue.

Having an user per application allows you to be more granular on permissions for each one, so that is actually not a bad practice.

If...

Same here. We use #1.

Of course you might have fluctuations in that if you change your normal pattern of data processing, but using the backup size trend is pretty accurate...

Maybe try:

sqlcmd -E -A -Q"alter login [sysdba1] with name = sa;"

As mentioned, having big tlog files because of lack of backups has its penalty on resources. It could be that it simply is trying to catch up to synchronize them?

sivaji (6/22/2010)

---

Being a programmer with no database knowledge/experience, I am requesting answers to following questions as I am kind of stuck now:

1. I have a doubt regarding sql server...

...

1) How do you have the mirroring setup, with or without witness (async or sync mirroring)?

The t-log size for the Database A would only grow if the mirroring is not...

More like this:

DECLARE @JOB TABLE(JOB_ID nvarchar(50))

DECLARE @JOBID nvarchar(50)

INSERT into @JOB (JOB_ID)

exec dbo.GetJobIDForReplicationSnapshot

set @JOBID = (select * from @job)

USE [msdb]

exec sp_start_job @job_id = @jobid

GO

Great stuff Randy. Thanks for the info you shared.

I had the same discussion with our SAN admin. He says that the I/O is spread over 10 disks anyway, so having different drives on the same SAN wouldn't make...

Nice question... with a twist from the QOD from the other day 😀