As I have mentioned before I am still trying to increase
the performance for a fact table load. This solution
could be my best bet.

The database recovery will be set to either Full or
Simple. I do not need the operation logged and I have
another tool that will log errors. Could I set the
database recovery model to bulk-logged and then perform
the insert and reset the database to its previous
recovery.

Would this increase performance for an insert ( setting
the recovery model to bulk-logged), and if so
can I easily reset the database recovery model
to its previous setting.

Yes, depending on your requirements for recoverability - remember, going to
bulk-logged or simple will reduce or eliminate your ability to do
point-in-time recoveries - most of the marts I support are not willing to
spend the dough for the additional storage to do t-logs (it would double or
triple the storage and backup requirements and they are fairly large, 100's
of GB's) - so we use simple - something to think about there.

You can easily script in the ALTER DATABASE and BACKUP commands to deal with
changing the recovery mode.


--
----------------------------------------------------
The views expressed here are my own
and not of my employer.
----------------------------------------------------
"Phil" <atec396@hotmail.com> wrote in message
news:0c9001c355f1$8e5e9b70$a501280a@phx.gbl...
> As I have mentioned before I am still trying to increase
> the performance for a fact table load. This solution
> could be my best bet.
>
> The database recovery will be set to either Full or
> Simple. I do not need the operation logged and I have
> another tool that will log errors. Could I set the
> database recovery model to bulk-logged and then perform
> the insert and reset the database to its previous
> recovery.
>
> Would this increase performance for an insert ( setting
> the recovery model to bulk-logged), and if so
> can I easily reset the database recovery model
> to its previous setting.
>