Non-intuitively, you need to set the backup strategy.

IWETHEY v. 0.3.0 | TODO

1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User

Welcome to IWETHEY!

Post #89,291

by rickw

3/18/03 9:17:21 PM

Non-intuitively, you need to set the backup strategy.

Now, I don't know how much flexibility you have in this regard since I don't have any idea what SAS expects.

How much detail gets put in the logs is determined by the restores that SQL server expects to do. Check BOL `ALTER DATABASE', the option you're looking for is recovery_option.

FAQ! We're scrod!

MS SQL Server: Logs & performance tuning? - (kmself) - (9) - Feb. 12, 2003, 07:57:48 PM EST

Two tacts... - (ChrisR) - (5) - Feb. 12, 2003, 08:33:28 PM EST

Probably shouldn't fight it though - (ChrisR) - (1) - Feb. 12, 2003, 08:43:22 PM EST

Havnt messed with SQLServer yet, question - (boxley) - Feb. 12, 2003, 09:53:21 PM EST

SAS rears its ugly head... - (kmself) - (1) - Feb. 13, 2003, 12:06:30 AM EST

SAS used to be able to shell out - run a "Load.Bat"? -NT - (CRConrad) - Feb. 13, 2003, 05:46:20 PM EST

"Tacks", actually. HTH! -NT - (CRConrad) - Feb. 14, 2003, 02:33:27 AM EST

Import vs. Load? BCP? - (gdaustin) - Feb. 14, 2003, 05:41:20 PM EST

Re: MS SQL Server: Logs & performance tuning? - (orion) - Feb. 17, 2003, 02:56:59 PM EST

Non-intuitively, you need to set the backup strategy. - (rickw) - March 18, 2003, 09:17:21 PM EST

iwethey.org

Man... licensed to kill gophers.
62 ms