This should either work, or not work. If it's intermittent, you likely have some network or resource issue.

I'm not sure what most people use, but I've used this for years,...

If it was security, I'd expect that it wouldn't update the original table and a rollback would occur. Is that what is happening?

Also, I'd write it in case multiple rows...

You're not necessarily duplicating lots of code. You might dup some, but you're also separating out and abstracting the functions to do a specific thing. That's what's done in many...

The editorial covered a couple things, one is that "cheating" devalues the exams for everyone. It isn't doing a friend a favor, nor yourself.

I don't have a problem with high...

DO NOT shrink the log after rebuilding. It's a waste of resources. The next reindex will grow it again.

The log should be sized for the peak load between log...

The thing I'd suggest is that you write two stored procedures, which is essentially two methods. Then if you want to build an abstraction, write a 3rd that takes both...

I'm not sure if the JET (Exchange/blue) engine is better than SQL. Or if it tackles a different problem, but from my basic understanding of Exchange, I'm not sure why...

The licensing isn't a big deal to me. You allow SQL Server as a part of any Exchange license, but only for Exchange databases. If you put something else on...

The thing is that SQL doesn't process row by row. It works on the entire table or result set at a time.

So what you can do is write conditions to...

I think you'd be better off doing the replacement in .NET, but you could use the replacements above.

The reason is that you're subtracting years, and as Michael's logic shows, you need to account for where in the current year you are in relation to the date of...

I believe you can use a comma to specify the server.

So for the sales server here: sales.sqlservercentral.com, 1899

would connect on port 1899.

What doesn't work? By that I mean what behavior is occurring. The trigger looks fine syntactically, but it won't work if multiple rows are updated.

Instead what you'd do is join...

You need to set up logging in the maintance plan, then check the text files that are created. They will have more details about what is wrong.

Thanks for the update.

I won't lock the topic, as someone might see something you could do better, but it's good to know what fixed it for you.