I'd open a case with Microsoft. I've never heard of anything remotely like this with SQL Server that wasn't some programming mistake.

True, you could need to match up SIDs with SQL logins.

Likely PowerShell could somehow run the script, take the ouput and pipe that in as a new batch for a...

Doh!

Yep, Datediff needs a type and then the arguments: http://msdn.microsoft.com/en-us/library/ms189794.aspx

The CASE is here: http://msdn.microsoft.com/en-us/library/ms181765.aspx

basically you can use it in the SELECT or the WHERE clauses as

CASE WHEN xx then...

I'd completely agree with Gail. Weekly isn't granular enough. I'd go with a better trace or logging.

Note that this is a manual process. If you add logins to the primary, it should be with a script, and you should amend the script to also add the...

Never seen anything like this. Unless you perhaps had implicit transactions off. Perhaps one started and didn't commit?

The SELECT should return the rows, however, if it's the same connection.

I would...

That is strange. I might set up a trace that logs activity to see what is happening here.

There is no IF() function in T-SQL. You're mixing something from another language in there.

SELECT

room_type,rate_start_date,rate_end_date,rate

, DATEDIFF( case when rate_end_date > '2011-04-16'

...

I like the idea of using a trace over time, but if you find databases that aren't in the default trace, I'd close them and set them offline. That way...

Note that you cannot be sure this will work. A DBA in control of the physical machine can always log in and remove logs, trace files, disable traces, etc. You...

No idea on IPStor.

However both database mirroring and log shipping do the same thing: ship transactions from the log to the other server. Log shipping works with log backups, so...

Kirin, Sapporo, Asahi, I'll take any of them with a hot bottle of sake.

Thanks for the update. That's good to know. Should have thought of looking for strange characters in there. My apologies.

I never restart instances unless there are patches and I need to. The log has nothing to do with restarts, as mentioned.

Read Gail's link and manage your transaction log.

You are correct. You gain nothing preserving it on SQL Server. Now depending on server memory, load, and the data set, it's likely in memory on SQL Server so it's...