![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Dear Professional, I would like to ask one quick question about data import through SSIS I am using SSIS Package that import 1 million of recrods in CHART database. I saw the log file size was too large. I modify the recovery model to Bulk Log but still everyday Log File size is too big. Is there any other settings I have to do to minimize the Log Space? Please advice. Thanks |
#3
| |||
| |||
|
|
If you don't have Transaction Log backups or Log Shipping, you can change the Recovery Model to SIMPLE before bulk loading operations. Before this action, executing a full backup would be preferable. Also, if this Transaction Log need space for regular operations then let it have what it needs. Don't let it to be shrunk and expanded especially to avoid physical file fragmentation and freezings that occur during expanding. -- Ekrem nsoy "Noor" <naissani (AT) hotmail (DOT) com>, iletisinde unu yazd, news:%23hgSSi6wJHA.1304 (AT) TK2MSFTNGP05 (DOT) phx.gbl... Dear Professional, I would like to ask one quick question about data import through SSIS I am using SSIS Package that import 1 million of recrods in CHART database. I saw the log file size was too large. I modify the recovery model to Bulk Log but still everyday Log File size is too big. Is there any other settings I have to do to minimize the Log Space? Please advice. Thanks |
#4
| |||
| |||
|
|
Then you shouldn't change the Recovery Model, otherwise your Log Shipping would be broken. You'll be keeping your Transaction Log file under your control by executing transaction log backups via your Log Shipping configuration. How about the transaction log backup intervals and what's the current size of your Transaction Log file and Data file of your database? -- Ekrem Önsoy "Rogers" <Rogers (AT) discussions (DOT) microsoft.com>, iletisinde sunu yazdi, news:C02FBF19-EF8E-4BDC-AB2E-AD39A12A15CB (AT) microsoft (DOT) com... There is a Log Shipping in Place. Can I think the .ldf file? Thanks "Ekrem Önsoy" wrote: If you don't have Transaction Log backups or Log Shipping, you can change the Recovery Model to SIMPLE before bulk loading operations. Before this action, executing a full backup would be preferable. Also, if this Transaction Log need space for regular operations then let it have what it needs. Don't let it to be shrunk and expanded especially to avoid physical file fragmentation and freezings that occur during expanding. -- Ekrem nsoy "Noor" <naissani (AT) hotmail (DOT) com>, iletisinde unu yazd, news:%23hgSSi6wJHA.1304 (AT) TK2MSFTNGP05 (DOT) phx.gbl... Dear Professional, I would like to ask one quick question about data import through SSIS I am using SSIS Package that import 1 million of recrods in CHART database. I saw the log file size was too large. I modify the recovery model to Bulk Log but still everyday Log File size is too big. Is there any other settings I have to do to minimize the Log Space? Please advice. Thanks |
#5
| |||
| |||
|
|
Currently. Log Shipping is in place and every hald an hour I take log backup and that has 100 MB in Size but the only problem is MyDB.ldf file size is 3 GB and MyDB.mdf file size is 25 GB. Can I shrink the MyDB.ldf, is there any impace on Log Shipping? Thanks "Ekrem Önsoy" <iletisim (AT) ekremREMOVE-THISonsoy (DOT) net> wrote in message news:7088C653-ABC9-457D-BD24-D5F18B93E02E (AT) microsoft (DOT) com... Then you shouldn't change the Recovery Model, otherwise your Log Shipping would be broken. You'll be keeping your Transaction Log file under your control by executing transaction log backups via your Log Shipping configuration. How about the transaction log backup intervals and what's the current size of your Transaction Log file and Data file of your database? -- Ekrem Önsoy "Rogers" <Rogers (AT) discussions (DOT) microsoft.com>, iletisinde sunu yazdi, news:C02FBF19-EF8E-4BDC-AB2E-AD39A12A15CB (AT) microsoft (DOT) com... There is a Log Shipping in Place. Can I think the .ldf file? Thanks "Ekrem Önsoy" wrote: If you don't have Transaction Log backups or Log Shipping, you can change the Recovery Model to SIMPLE before bulk loading operations. Before this action, executing a full backup would be preferable. Also, if this Transaction Log need space for regular operations then let it have what it needs. Don't let it to be shrunk and expanded especially to avoid physical file fragmentation and freezings that occur during expanding. -- Ekrem nsoy "Noor" <naissani (AT) hotmail (DOT) com>, iletisinde unu yazd, news:%23hgSSi6wJHA.1304 (AT) TK2MSFTNGP05 (DOT) phx.gbl... Dear Professional, I would like to ask one quick question about data import through SSIS I am using SSIS Package that import 1 million of recrods in CHART database. I saw the log file size was too large. I modify the recovery model to Bulk Log but still everyday Log File size is too big. Is there any other settings I have to do to minimize the Log Space? Please advice. Thanks |
#6
| |||
| |||
|
|
I think 3GB for your Transaction Log file looks fine, I would leave it as it is; also probably I would set its initial size as 5GB and enable Instant File Initialization. Shrinking your transaction log file does not break your Log Shipping as long as you don't back up your Transaction Log manually or using another job other than Log Shipping' s backup job. -- Ekrem Önsoy "Noor" <naissani (AT) hotmail (DOT) com>, iletisinde şunu yazdı, news:%230pE2qHxJHA.4364 (AT) TK2MSFTNGP03 (DOT) phx.gbl... Currently. Log Shipping is in place and every hald an hour I take log backup and that has 100 MB in Size but the only problem is MyDB.ldf file size is 3 GB and MyDB.mdf file size is 25 GB. Can I shrink the MyDB.ldf, is there any impace on Log Shipping? Thanks "Ekrem Önsoy" <iletisim (AT) ekremREMOVE-THISonsoy (DOT) net> wrote in message news:7088C653-ABC9-457D-BD24-D5F18B93E02E (AT) microsoft (DOT) com... Then you shouldn't change the Recovery Model, otherwise your Log Shipping would be broken. You'll be keeping your Transaction Log file under your control by executing transaction log backups via your Log Shipping configuration. How about the transaction log backup intervals and what's the current size of your Transaction Log file and Data file of your database? -- Ekrem Önsoy "Rogers" <Rogers (AT) discussions (DOT) microsoft.com>, iletisinde sunu yazdi, news:C02FBF19-EF8E-4BDC-AB2E-AD39A12A15CB (AT) microsoft (DOT) com... There is a Log Shipping in Place. Can I think the .ldf file? Thanks "Ekrem Önsoy" wrote: If you don't have Transaction Log backups or Log Shipping, you can change the Recovery Model to SIMPLE before bulk loading operations. Before this action, executing a full backup would be preferable. Also, if this Transaction Log need space for regular operations then let it have what it needs. Don't let it to be shrunk and expanded especially to avoid physical file fragmentation and freezings that occur during expanding. -- Ekrem nsoy "Noor" <naissani (AT) hotmail (DOT) com>, iletisinde unu yazd, news:%23hgSSi6wJHA.1304 (AT) TK2MSFTNGP05 (DOT) phx.gbl... Dear Professional, I would like to ask one quick question about data import through SSIS I am using SSIS Package that import 1 million of recrods in CHART database. I saw the log file size was too large. I modify the recovery model to Bulk Log but still everyday Log File size is too big. Is there any other settings I have to do to minimize the Log Space? Please advice. Thanks |
#7
| |||
| |||
|
|
I think 3GB for your Transaction Log file looks fine, I would leave it as it is; also probably I would set its initial size as 5GB and enable Instant File Initialization. Shrinking your transaction log file does not break your Log Shipping as long as you don't back up your Transaction Log manually or using another job other than Log Shipping' s backup job. -- Ekrem Önsoy "Noor" <naissani (AT) hotmail (DOT) com>, iletisinde şunu yazdı, news:%230pE2qHxJHA.4364 (AT) TK2MSFTNGP03 (DOT) phx.gbl... Currently. Log Shipping is in place and every hald an hour I take log backup and that has 100 MB in Size but the only problem is MyDB.ldf file size is 3 GB and MyDB.mdf file size is 25 GB. Can I shrink the MyDB.ldf, is there any impace on Log Shipping? Thanks "Ekrem Önsoy" <iletisim (AT) ekremREMOVE-THISonsoy (DOT) net> wrote in message news:7088C653-ABC9-457D-BD24-D5F18B93E02E (AT) microsoft (DOT) com... Then you shouldn't change the Recovery Model, otherwise your Log Shipping would be broken. You'll be keeping your Transaction Log file under your control by executing transaction log backups via your Log Shipping configuration. How about the transaction log backup intervals and what's the current size of your Transaction Log file and Data file of your database? -- Ekrem Önsoy "Rogers" <Rogers (AT) discussions (DOT) microsoft.com>, iletisinde sunu yazdi, news:C02FBF19-EF8E-4BDC-AB2E-AD39A12A15CB (AT) microsoft (DOT) com... There is a Log Shipping in Place. Can I think the .ldf file? Thanks "Ekrem Önsoy" wrote: If you don't have Transaction Log backups or Log Shipping, you can change the Recovery Model to SIMPLE before bulk loading operations. Before this action, executing a full backup would be preferable. Also, if this Transaction Log need space for regular operations then let it have what it needs. Don't let it to be shrunk and expanded especially to avoid physical file fragmentation and freezings that occur during expanding. -- Ekrem nsoy "Noor" <naissani (AT) hotmail (DOT) com>, iletisinde unu yazd, news:%23hgSSi6wJHA.1304 (AT) TK2MSFTNGP05 (DOT) phx.gbl... Dear Professional, I would like to ask one quick question about data import through SSIS I am using SSIS Package that import 1 million of recrods in CHART database. I saw the log file size was too large. I modify the recovery model to Bulk Log but still everyday Log File size is too big. Is there any other settings I have to do to minimize the Log Space? Please advice. Thanks |
#8
| |||
| |||
|
|
What do you mean by enable Instant File Initialization. "Ekrem Önsoy" <iletisim (AT) ekremREMOVE-THISonsoy (DOT) net> wrote in message news:uc0CqYKxJHA.4636 (AT) TK2MSFTNGP05 (DOT) phx.gbl... I think 3GB for your Transaction Log file looks fine, I would leave it as it is; also probably I would set its initial size as 5GB and enable Instant File Initialization. Shrinking your transaction log file does not break your Log Shipping as long as you don't back up your Transaction Log manually or using another job other than Log Shipping' s backup job. -- Ekrem Önsoy "Noor" <naissani (AT) hotmail (DOT) com>, iletisinde şunu yazdı, news:%230pE2qHxJHA.4364 (AT) TK2MSFTNGP03 (DOT) phx.gbl... Currently. Log Shipping is in place and every hald an hour I take log backup and that has 100 MB in Size but the only problem is MyDB.ldf file size is 3 GB and MyDB.mdf file size is 25 GB. Can I shrink the MyDB.ldf, is there any impace on Log Shipping? Thanks "Ekrem Önsoy" <iletisim (AT) ekremREMOVE-THISonsoy (DOT) net> wrote in message news:7088C653-ABC9-457D-BD24-D5F18B93E02E (AT) microsoft (DOT) com... Then you shouldn't change the Recovery Model, otherwise your Log Shipping would be broken. You'll be keeping your Transaction Log file under your control by executing transaction log backups via your Log Shipping configuration. How about the transaction log backup intervals and what's the current size of your Transaction Log file and Data file of your database? -- Ekrem Önsoy "Rogers" <Rogers (AT) discussions (DOT) microsoft.com>, iletisinde sunu yazdi, news:C02FBF19-EF8E-4BDC-AB2E-AD39A12A15CB (AT) microsoft (DOT) com... There is a Log Shipping in Place. Can I think the .ldf file? Thanks "Ekrem Önsoy" wrote: If you don't have Transaction Log backups or Log Shipping, you can change the Recovery Model to SIMPLE before bulk loading operations. Before this action, executing a full backup would be preferable. Also, if this Transaction Log need space for regular operations then let it have what it needs. Don't let it to be shrunk and expanded especially to avoid physical file fragmentation and freezings that occur during expanding. -- Ekrem nsoy "Noor" <naissani (AT) hotmail (DOT) com>, iletisinde unu yazd, news:%23hgSSi6wJHA.1304 (AT) TK2MSFTNGP05 (DOT) phx.gbl... Dear Professional, I would like to ask one quick question about data import through SSIS I am using SSIS Package that import 1 million of recrods in CHART database. I saw the log file size was too large. I modify the recovery model to Bulk Log but still everyday Log File size is too big. Is there any other settings I have to do to minimize the Log Space? Please advice. Thanks |
![]() |
| Thread Tools | |
| Display Modes | |
| |