Sanjay

You may be able to claw back some space by deleting unneeded files from D, or shrinking any data or log files that you know are too large and will...

If you made schema1 the default schema for user1, that'll only work for user1, not for you as well, unless your own default schema also happens to be schema1.

John

Did you remove it from the SELECT list and the GROUP BY clause?

John

Edit - corrected italics tags

Can you not just dispense with the Year column? What do you need it to represent?

John

Definitely don't have it running, then.

John

I wouldn't run it as required - I would either use it or not use it. It only works for named instance, so if you only have a default...

It's because for those particular values of date, you have two separate values of Year. Presumably this is caused by arrival date and departure date being in different years.

John

Edvard

Yes. Can you imagine the confusion if it were any other way? You wouldn't know whether you were getting old values or new values!

John

Edvard

Yes, that's how it works. Try declaring @starttime and @endtime variables and setting them to the new values. You can then use them in the update query instead...

I don't know. There's a ConnectionString column in the DataSource table, but it's not in plain text. Like I said, I don't recommend hacking the tables, and I...

What sort of data source do your reports use - embedded or shared? If you use a shared data source then you only need to change it in one...

That's right - unless IMPLICIT_TRANSACTIONS is ON for your connection. It's not the default, so it's unlikely to be on unless you consciously set it to be.

John

The best way to find out is to try it, of course. If you did, you'd get a message saying that the ROLLBACK has no corresponding BEGIN TRANSACTION, which,...

That's right. But don't take my word for it - do some reading on merge replication, and then set up a test if you think it fits your requirements.

John

No, with merge replication you read and write against your local database and the conflicts are resolved and changes merged so that the two (or more) databases stay in sync.

John