insert data in SQL Server thorugh SSIS source and destination without effecting transaction log of sql server

  • i want to insert data from one sql server table to another table which is in another server in sql server.

    but when i insert data i dont want to effect or increase transaction log of the destination sever.

    Is there any way . As i know a bit that there is an option in ssis called Shrink but i dont know whether it works and is there some other way since my data is huge.

  • scottichrosaviakosmos (2/21/2011)


    i want to insert data from one sql server table to another table which is in another server in sql server.

    but when i insert data i dont want to effect or increase transaction log of the destination sever.

    Is there any way . As i know a bit that there is an option in ssis called Shrink but i dont know whether it works and is there some other way since my data is huge.

    Every change (in data or schema) in SQL Server goes to the log file. Every one. How much of a nuisance they are while they're there depends on a few things, such as recovery type, backup frequency, and methods used to insert data (for example, minimally logged vs. fully logged)... but no, you can't avoid the log file.

    What are your concerns regarding the log file? Perhaps we can help you out with using it in a way that'll be less troublesome.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • As Craig mentioned, everything goes through the transaction log. That's how database consistency and ACID is enforced. There are tricks to minimize the impact, but depending on what you are doing, some may or may not work.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply