Hi,

Thanks steve,

Could you say a little more about how "sawpping down" method works. Alsois the PAE switch seperate from the /3gb switch?

Thanks,

Jules

Is my post not clear? Do i need to use switch? or can i explicitly drop partitions?

nice one mark. Didnt know you could use partition with count.

for a large dataset would it not be better to insertt he results of the cte1 into a temp table and run the max query on that

but this means having another statement. I could use a max subquery to get these values in a second statement which i think would perform better than a cross...

i hope its clear that its the second column i want to get. the first one is gerenerated by a rownumber function

nice one jeff. So dropping a big table hardly uses any CPU at all. super

OK Ta

of course but this would mean losing the transaction since the back up was taken. It doesnt sound like there is an elegant way of achieveing what i am trying...

yes abnd what technology would you recommend for keeping the staging enviromment in sync with the production enviromment?

ok so for a big roll out the options are take the live box down for a while or run the scripts on live and hope the testers did their...

David my point is to use the fail over as a place to roll out changes before switching the secondary to be the master. So avoiding the load on the...

So mirroring and log shipping will allow me to run schema updates on the secondary or slave DBs whilst the transactional replication will continue feeding the uneffected tables?

What are my options for a high availability system that requires regular roll out of schema changes. I am looking for an HA solution that allows hot fixing of SQL...

Create a 'data source'

then create a 'data source view'.

This can be done in SSBIS or SSMS