Showing posts with label notrecorded. Show all posts
Showing posts with label notrecorded. Show all posts

Wednesday, March 21, 2012

Exclude table from transaction log

Hi
Does anyone know if it is possible that changes to a specific table are not
recorded in the transaction log while changes to other tables are ?
If yes how can this be done?
Thanks
Daniel
Message posted via http://www.droptable.comThat's not possible. Why do you want to do this?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
"DANR via droptable.com" <u26179@.uwe> wrote in message
news:662d81586fb67@.uwe...
Hi
Does anyone know if it is possible that changes to a specific table are not
recorded in the transaction log while changes to other tables are ?
If yes how can this be done?
Thanks
Daniel
Message posted via http://www.droptable.com|||Hi,
No. We can not do that. SQL Server engine by itself will log all the
transactions in to transaction log file.
Thanks
Hari
SQL Server MVP
"DANR via droptable.com" <u26179@.uwe> wrote in message
news:662d81586fb67@.uwe...
> Hi
> Does anyone know if it is possible that changes to a specific table are
> not
> recorded in the transaction log while changes to other tables are ?
> If yes how can this be done?
> Thanks
> Daniel
> --
> Message posted via http://www.droptable.com
>|||Hi Tom
Because I have a table were I register several informations with thousands o
f
records but the information is not really critical and if something goes
wrong I don't need to recover that information.
This information is increasing the size of the transaction log without being
really necessary.
Thanks
Daniel
Tom Moreau wrote:
>That's not possible. Why do you want to do this?
>Hi
>Does anyone know if it is possible that changes to a specific table are not
>recorded in the transaction log while changes to other tables are ?
>If yes how can this be done?
>Thanks
>Daniel
Message posted via http://www.droptable.com|||Ok Hari
Thanks
Daniel
Hari Prasad wrote:[vbcol=seagreen]
>Hi,
>No. We can not do that. SQL Server engine by itself will log all the
>transactions in to transaction log file.
>Thanks
>Hari
>SQL Server MVP
>
>[quoted text clipped - 5 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||If you don't need that this table is time-correlated with the rest of the ta
ble in your backups,
consider putting it in its own database. Also, this database can be in simpl
e recovery mode and you
can investigate if it is possible to input the data using a minimally logged
operation (bulk loading
is probably the best bet).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"DANR via droptable.com" <u26179@.uwe> wrote in message news:662ee8ef93f81@.uwe...reen">
> Hi Tom
> Because I have a table were I register several informations with thousands
of
> records but the information is not really critical and if something goes
> wrong I don't need to recover that information.
> This information is increasing the size of the transaction log without bei
ng
> really necessary.
> Thanks
> Daniel
>
> Tom Moreau wrote:
> --
> Message posted via http://www.droptable.com
>|||Hi Tibor
Thanks for your sugestion. I already thought using that approach.
I just asked because maybe someone know other way.
Thanks to all
Regards
Daniel
Tibor Karaszi wrote:[vbcol=seagreen]
>If you don't need that this table is time-correlated with the rest of the t
able in your backups,
>consider putting it in its own database. Also, this database can be in simp
le recovery mode and you
>can investigate if it is possible to input the data using a minimally logge
d operation (bulk loading
>is probably the best bet).
>
>[quoted text clipped - 16 lines]
Message posted via http://www.droptable.com