Hehe, you're absolute right about testing! I certainly will, it's just @#$@$@##$@* busy here... but I know I must take the time to do the tests.

Thanks!

Hi,

Thanks for your replies.

Clear, thx!

Last...

Not yet. I hoping to do some experiments with 64 bit ACE over this upcoming weekend. Thanks for the feedback on the 32 bit stuff. I'm glad they didn't mess...

You can also use COUNT(1) instead of COUNT(*) or COUNT(<colname>).

Thanks for y'r answers... i'll be looking into it right now!

Thanks again! I will increase the number of times I backup the transaction logs.... sounds logical, and better if the transaction log doesn't grow that fast.

Thanks for all your replies. I checked out article from Paul Randal and I believe I have a better understanding of the matter. Still I have no practical answer how...

Thanks for all your replies.

I wanted to do a local backup, but I saw that there's not enough diskspace. That's why I backup across the network - to a...

Thanks to all for your input! Especially SARGABLE has given us new insights!!

Raymond

Thanks to everyone for comments, I've become a wiser man!

Ray

Hi,

Actually what I would like best is a Stored Procedure I wrote getting fired; it logs all error info into a logfile. Something like this:

TRIGGER ON UPDATE, INSERT

BEGIN TRY

...

I've tried several things, with no result.

I am curious, am I asking something stupid? All I want, as DBA, that when a trigger fails, the faillure gets logged so...

Thanks for your answer.

I tried it, but now I get:

---------------------------

Microsoft SQL Server Management Studio

---------------------------

No row was updated.

The data in row 134 was not committed.

Error Source: .Net SqlClient Data Provider.

Error Message:...

Thanks for your reply.... it's clear!

Ray

It's working!

Thanks a 10^6

Ray