Thanks for the vote of confidence Jeff - taking up the pen on the topic of permissions is something I'll have to deliberate over. Hopefully I can find some...

Thanks for eyeballing this Jeff.

Yes, when executing within the context of the 'dev_role' role the following 2 statements fail as intended:create table foo.bar (i int);

execute as user = 'dbo';

And the...

Me think know ansur:

Not quite what I was going for to begin with, but these 2 solutions are probably more sensible than [font="Courier New"]GRANT ALTER to dev_role[/font]:

Solution 1 (no explicit...

Thanks - that's some great info to chew on! (I'm only seeing 1 link..?)

However, it doesn't quite seem to answer my question on the mechanics of how it maximizes...

Eirikur Eiriksson (8/25/2014)

---

jjturner (8/25/2014)

---

Eirikur Eiriksson (8/25/2014)

---

jjturner (8/25/2014)

---

Yes, apologies for the tacit generalization (backup ~ backup/restore)

So further to the point, I'm having this DEV recovery model switch over to FULL a...

Eirikur Eiriksson (8/25/2014)

---

jjturner (8/25/2014)

---

Yes, apologies for the tacit generalization (backup ~ backup/restore)

So further to the point, I'm having this DEV recovery model switch over to FULL a number of days...

Yes, apologies for the tacit generalization (backup ~ backup/restore)

So further to the point, I'm having this DEV recovery model switch over to FULL a number of days after it got...

Yes, thanks for the sanity check -

Actually I'm running Mr. Hallengren's scripts on PROD. 1 weekly full, daily diff, hourly log -- works a charm!

The other thing to note,...

Lynn Pettis (8/25/2014)

---

Backup processes will not change the recovery model of a database. The only way this can happen is if someone goes in and manually modifies the recovery...

Thanks Lynn - I'll have to do some more digging then. I'm still suspicious though since no one else would think to alter the RM and I definitely didn't...

aha - that's sneaky!

Thanks for pinning this down for me John!

Thanks folks for looking into this for me -

I'm using Ola Hallengren's backup scripts and the @CopyOnly switch has not been altered from its default of 'N':

sqlcmd -E -S $(ESCAPE_SQUOTE(SRVR))...

use master;

go

restore database new_loc_testdb

from disk = '\\backup_dir\full\prod_full_20140803_233000.bak'

with

--replace

checksum

,move 'prod01' to 'e:\temp_restore\data01.mdf'

,move 'prod02' to 'e:\temp_restore\data02.ndf'

,move 'prod03' to 'e:\temp_restore\data03.ndf'

,move 'prod04' to 'e:\temp_restore\data04.ndf'

,move 'prod_log' to 'e:\temp_restore\testlog.ldf'

,norecovery

go

restore database new_loc_testdb

from disk = '\\backup_dir\diff\prod_diff_20140806_233000.bak'

with

checksum

,move 'prod01' to 'e:\temp_restore\data01.mdf'

,move...

Linked Server, O Linked Server, wherefore art thou Linked Server? Be some other connection design! :crazy:

Nice post Thomas, this is sorely needed information. Thank you!

closing this out and trying msdn