sorry.....I meant to post this in SQL 2k8 area, but the question still remains the same.....

GAJ

nothing looks dreadfully wrong to me but "try" this.....

1) remove the rowlock hints (worth a shot)

2) remove the explicit begin transaction and committ\rollback (they are only wrapping single statements anyway)

update...

there's likely more to this picture....

- is this in a transaction where other work is occuring?

- have you tried removing the rowlock hint ?

- is this only...

I agree with what you are all saying.

We are currently debating this here as well....

it's a tradeoff...

Engineering\Coding Vs DBA state of mind and maintainability

I'm stickin to my guns here and...

I'm making a decision now at my current workplace.

Folks at ERStudio wont return my calls, etc.

Probably gonna go with ERWin just by default.

The place I work is using EA and having used ERWin and ERStudio extensively in the past, I absolutely HATE EA.

This could very well be a "You dont know how...

Yeah It would depend on the requirements for the reporting environment (mostly the lag time that is acceptable).

LogShipping would be a great solution in most cases.

gaj

lol

yeah. I usually leave em at home.

thanks again

GAJ

Thanks Rowland,

I agree.

I'd love to hear more discussion on this topic.

Never an easy one to handle....

cheers,

Greg J

I agree.

I'm not a fan of this in the world of RDMS's

It's "cool", etc. but it doesnt seem practical.

imagine writing queries and reports against the data, etc ?

blech.

GAJ

wow...that's great news.

whole reason for the article....Mission accomplished !

🙂

GAJ

Thanks Everyone,

I've been in Vegas the past few days for the NASCAR so I'm a little late in replying.

Thanks for the comments and discussion.

Greg J

yeah I agree.

changing the RAID Level will not do too much at this point.

now adding Spindles (Disks) may give you a big improvement, but now youre talkin bucks.

Greg J

Hadn't considered it but it certainly is a good idea

good question...

that was exactly why we went with mirroring.

SQL Server Mirroring automatically copies the transaction logs from your source to the target.

the logs are backed up as part of normal...