Perform a Smart Publish or Republish on a brand new Sitecore instance?












4















I was reading What is the difference between republish, smart publish and incremental publishes? and now I'm wondering if I'm better running a republish (as I always did) or a smart publish on a new Sitecore instance.



I had in mind that by running a republish I was skipping all the compares between master and web which are done by the smart publish option.



But now I realize that there are already a bunch of items on a brand new Sitecore instance which are already on both master and web, and it makes me think if a smart publish could be more efficient since it won't copy those items above mentioned.



Basically, what is the most efficient option on a new Sitecore instance?










share|improve this question





























    4















    I was reading What is the difference between republish, smart publish and incremental publishes? and now I'm wondering if I'm better running a republish (as I always did) or a smart publish on a new Sitecore instance.



    I had in mind that by running a republish I was skipping all the compares between master and web which are done by the smart publish option.



    But now I realize that there are already a bunch of items on a brand new Sitecore instance which are already on both master and web, and it makes me think if a smart publish could be more efficient since it won't copy those items above mentioned.



    Basically, what is the most efficient option on a new Sitecore instance?










    share|improve this question



























      4












      4








      4








      I was reading What is the difference between republish, smart publish and incremental publishes? and now I'm wondering if I'm better running a republish (as I always did) or a smart publish on a new Sitecore instance.



      I had in mind that by running a republish I was skipping all the compares between master and web which are done by the smart publish option.



      But now I realize that there are already a bunch of items on a brand new Sitecore instance which are already on both master and web, and it makes me think if a smart publish could be more efficient since it won't copy those items above mentioned.



      Basically, what is the most efficient option on a new Sitecore instance?










      share|improve this question
















      I was reading What is the difference between republish, smart publish and incremental publishes? and now I'm wondering if I'm better running a republish (as I always did) or a smart publish on a new Sitecore instance.



      I had in mind that by running a republish I was skipping all the compares between master and web which are done by the smart publish option.



      But now I realize that there are already a bunch of items on a brand new Sitecore instance which are already on both master and web, and it makes me think if a smart publish could be more efficient since it won't copy those items above mentioned.



      Basically, what is the most efficient option on a new Sitecore instance?







      publishing






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 9 hours ago









      Hishaam Namooya

      6,7291627




      6,7291627










      asked 13 hours ago









      Hugo SantosHugo Santos

      712118




      712118






















          2 Answers
          2






          active

          oldest

          votes


















          3














          The "Republish" required only when bringing a new web database online or creating a new publishing target etc. Copied the below highlighted paragraph from Sitecore document,




          Republishing removes all obsolete versions from the target database.
          You can use republishing to bring a new web database online, to
          restore a backup of the master database, and to add a new content
          language, a new publishing target, or other system items to the
          website.




          I guess in your case, you are not creating a new web database/publishing target, you are planning to use the web DB which comes with the Sitecore installation. So technically "Smart Publish" should be efficient.



          I Just ran the Smart and Republish in two plain Sitecore 8.2 local instances separately, the time taken to complete the publish might vary due to various external parameters as well, so ignore the timing in the below logs. But the Republish is always overwriting/updating around 4625 items in a plain instance which might be an additional overhead, because those are already available in the web db.



          **Sample Smart Publish logs from plain instance**
          21148 14:18:00 INFO Finished [Publishing] - ProcessQueue in 5773 ms
          21148 14:18:00 INFO Publish Mode : Smart
          21148 14:18:00 INFO Created : 0
          21148 14:18:00 INFO Updated : 0
          21148 14:18:00 INFO Deleted : 0
          21148 14:18:00 INFO Skipped : 4627

          **Sample Republish logs from plain instance**
          18628 14:25:59 INFO Finished [Publishing] - ProcessQueue in 260689 ms
          18628 14:25:59 INFO Publish Mode : Full
          18628 14:25:59 INFO Created : 0
          18628 14:25:59 INFO Updated : 4625
          18628 14:25:59 INFO Deleted : 0
          18628 14:25:59 INFO Skipped : 2


          Note - Whatever changes you make on top of the instance, only that needs to be migrated/published to the web db and "Smart Publish" can do that.






          share|improve this answer

































            2














            If you are creating a new Sitecore Instance, I would recommend to use a Full Site Publish as per Sitecore recommendation from the installation guide.



            The reason why a Full Site Publish is recommended is because you'll make sure that the master and web databases are sync, i.e, items on master is present on web. I noticed that the Full Site Publish on a new Sitecore instance does not take long to run and also, I see that there are new items get created on the web database.



            Moreover, if you have an extremely large number of changes (new instance or migrated/rewrote your entire site) the Smart Publish could also take a very long time since not only will it have to update almost all the items but it will also have to do the comparisons of each item.



            Then, you can use incremental or smart publish afterwards. Normally, I tend to create an auto-publish agent which use the incremental publish. The job is ran every 1 hour to push changes live.






            share|improve this answer


























            • "because you'll make sure that the master and web databases are sync" so that means that the smart publish may result in a not synced state?

              – Hugo Santos
              9 hours ago











            • Smart Publish makes use of the revision field. So, if the revision id is same, it will skip the item. But republish will assure that all items are exactly the same on the target database (not taking into consideration workflow here).

              – Hishaam Namooya
              9 hours ago











            • But since we are talking about a brand new Sitecore instance, the revision ID should not cause any issue (famous last words)... Did you have experienced something different in real life?

              – Hugo Santos
              9 hours ago











            • As far as i know, it should not be a problem. I’ll try to test the performance of both in the coming days and I’ll update the answer. Truly speaking i think republish and smart publish on new instance may take approximately the same amount of time as the root item for smart publish will be the sitecore item. So it will compare each item while full publish will just push the item to web

              – Hishaam Namooya
              9 hours ago












            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "664"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f18005%2fperform-a-smart-publish-or-republish-on-a-brand-new-sitecore-instance%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            3














            The "Republish" required only when bringing a new web database online or creating a new publishing target etc. Copied the below highlighted paragraph from Sitecore document,




            Republishing removes all obsolete versions from the target database.
            You can use republishing to bring a new web database online, to
            restore a backup of the master database, and to add a new content
            language, a new publishing target, or other system items to the
            website.




            I guess in your case, you are not creating a new web database/publishing target, you are planning to use the web DB which comes with the Sitecore installation. So technically "Smart Publish" should be efficient.



            I Just ran the Smart and Republish in two plain Sitecore 8.2 local instances separately, the time taken to complete the publish might vary due to various external parameters as well, so ignore the timing in the below logs. But the Republish is always overwriting/updating around 4625 items in a plain instance which might be an additional overhead, because those are already available in the web db.



            **Sample Smart Publish logs from plain instance**
            21148 14:18:00 INFO Finished [Publishing] - ProcessQueue in 5773 ms
            21148 14:18:00 INFO Publish Mode : Smart
            21148 14:18:00 INFO Created : 0
            21148 14:18:00 INFO Updated : 0
            21148 14:18:00 INFO Deleted : 0
            21148 14:18:00 INFO Skipped : 4627

            **Sample Republish logs from plain instance**
            18628 14:25:59 INFO Finished [Publishing] - ProcessQueue in 260689 ms
            18628 14:25:59 INFO Publish Mode : Full
            18628 14:25:59 INFO Created : 0
            18628 14:25:59 INFO Updated : 4625
            18628 14:25:59 INFO Deleted : 0
            18628 14:25:59 INFO Skipped : 2


            Note - Whatever changes you make on top of the instance, only that needs to be migrated/published to the web db and "Smart Publish" can do that.






            share|improve this answer






























              3














              The "Republish" required only when bringing a new web database online or creating a new publishing target etc. Copied the below highlighted paragraph from Sitecore document,




              Republishing removes all obsolete versions from the target database.
              You can use republishing to bring a new web database online, to
              restore a backup of the master database, and to add a new content
              language, a new publishing target, or other system items to the
              website.




              I guess in your case, you are not creating a new web database/publishing target, you are planning to use the web DB which comes with the Sitecore installation. So technically "Smart Publish" should be efficient.



              I Just ran the Smart and Republish in two plain Sitecore 8.2 local instances separately, the time taken to complete the publish might vary due to various external parameters as well, so ignore the timing in the below logs. But the Republish is always overwriting/updating around 4625 items in a plain instance which might be an additional overhead, because those are already available in the web db.



              **Sample Smart Publish logs from plain instance**
              21148 14:18:00 INFO Finished [Publishing] - ProcessQueue in 5773 ms
              21148 14:18:00 INFO Publish Mode : Smart
              21148 14:18:00 INFO Created : 0
              21148 14:18:00 INFO Updated : 0
              21148 14:18:00 INFO Deleted : 0
              21148 14:18:00 INFO Skipped : 4627

              **Sample Republish logs from plain instance**
              18628 14:25:59 INFO Finished [Publishing] - ProcessQueue in 260689 ms
              18628 14:25:59 INFO Publish Mode : Full
              18628 14:25:59 INFO Created : 0
              18628 14:25:59 INFO Updated : 4625
              18628 14:25:59 INFO Deleted : 0
              18628 14:25:59 INFO Skipped : 2


              Note - Whatever changes you make on top of the instance, only that needs to be migrated/published to the web db and "Smart Publish" can do that.






              share|improve this answer




























                3












                3








                3







                The "Republish" required only when bringing a new web database online or creating a new publishing target etc. Copied the below highlighted paragraph from Sitecore document,




                Republishing removes all obsolete versions from the target database.
                You can use republishing to bring a new web database online, to
                restore a backup of the master database, and to add a new content
                language, a new publishing target, or other system items to the
                website.




                I guess in your case, you are not creating a new web database/publishing target, you are planning to use the web DB which comes with the Sitecore installation. So technically "Smart Publish" should be efficient.



                I Just ran the Smart and Republish in two plain Sitecore 8.2 local instances separately, the time taken to complete the publish might vary due to various external parameters as well, so ignore the timing in the below logs. But the Republish is always overwriting/updating around 4625 items in a plain instance which might be an additional overhead, because those are already available in the web db.



                **Sample Smart Publish logs from plain instance**
                21148 14:18:00 INFO Finished [Publishing] - ProcessQueue in 5773 ms
                21148 14:18:00 INFO Publish Mode : Smart
                21148 14:18:00 INFO Created : 0
                21148 14:18:00 INFO Updated : 0
                21148 14:18:00 INFO Deleted : 0
                21148 14:18:00 INFO Skipped : 4627

                **Sample Republish logs from plain instance**
                18628 14:25:59 INFO Finished [Publishing] - ProcessQueue in 260689 ms
                18628 14:25:59 INFO Publish Mode : Full
                18628 14:25:59 INFO Created : 0
                18628 14:25:59 INFO Updated : 4625
                18628 14:25:59 INFO Deleted : 0
                18628 14:25:59 INFO Skipped : 2


                Note - Whatever changes you make on top of the instance, only that needs to be migrated/published to the web db and "Smart Publish" can do that.






                share|improve this answer















                The "Republish" required only when bringing a new web database online or creating a new publishing target etc. Copied the below highlighted paragraph from Sitecore document,




                Republishing removes all obsolete versions from the target database.
                You can use republishing to bring a new web database online, to
                restore a backup of the master database, and to add a new content
                language, a new publishing target, or other system items to the
                website.




                I guess in your case, you are not creating a new web database/publishing target, you are planning to use the web DB which comes with the Sitecore installation. So technically "Smart Publish" should be efficient.



                I Just ran the Smart and Republish in two plain Sitecore 8.2 local instances separately, the time taken to complete the publish might vary due to various external parameters as well, so ignore the timing in the below logs. But the Republish is always overwriting/updating around 4625 items in a plain instance which might be an additional overhead, because those are already available in the web db.



                **Sample Smart Publish logs from plain instance**
                21148 14:18:00 INFO Finished [Publishing] - ProcessQueue in 5773 ms
                21148 14:18:00 INFO Publish Mode : Smart
                21148 14:18:00 INFO Created : 0
                21148 14:18:00 INFO Updated : 0
                21148 14:18:00 INFO Deleted : 0
                21148 14:18:00 INFO Skipped : 4627

                **Sample Republish logs from plain instance**
                18628 14:25:59 INFO Finished [Publishing] - ProcessQueue in 260689 ms
                18628 14:25:59 INFO Publish Mode : Full
                18628 14:25:59 INFO Created : 0
                18628 14:25:59 INFO Updated : 4625
                18628 14:25:59 INFO Deleted : 0
                18628 14:25:59 INFO Skipped : 2


                Note - Whatever changes you make on top of the instance, only that needs to be migrated/published to the web db and "Smart Publish" can do that.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 5 hours ago

























                answered 11 hours ago









                GobinathGobinath

                69013




                69013























                    2














                    If you are creating a new Sitecore Instance, I would recommend to use a Full Site Publish as per Sitecore recommendation from the installation guide.



                    The reason why a Full Site Publish is recommended is because you'll make sure that the master and web databases are sync, i.e, items on master is present on web. I noticed that the Full Site Publish on a new Sitecore instance does not take long to run and also, I see that there are new items get created on the web database.



                    Moreover, if you have an extremely large number of changes (new instance or migrated/rewrote your entire site) the Smart Publish could also take a very long time since not only will it have to update almost all the items but it will also have to do the comparisons of each item.



                    Then, you can use incremental or smart publish afterwards. Normally, I tend to create an auto-publish agent which use the incremental publish. The job is ran every 1 hour to push changes live.






                    share|improve this answer


























                    • "because you'll make sure that the master and web databases are sync" so that means that the smart publish may result in a not synced state?

                      – Hugo Santos
                      9 hours ago











                    • Smart Publish makes use of the revision field. So, if the revision id is same, it will skip the item. But republish will assure that all items are exactly the same on the target database (not taking into consideration workflow here).

                      – Hishaam Namooya
                      9 hours ago











                    • But since we are talking about a brand new Sitecore instance, the revision ID should not cause any issue (famous last words)... Did you have experienced something different in real life?

                      – Hugo Santos
                      9 hours ago











                    • As far as i know, it should not be a problem. I’ll try to test the performance of both in the coming days and I’ll update the answer. Truly speaking i think republish and smart publish on new instance may take approximately the same amount of time as the root item for smart publish will be the sitecore item. So it will compare each item while full publish will just push the item to web

                      – Hishaam Namooya
                      9 hours ago
















                    2














                    If you are creating a new Sitecore Instance, I would recommend to use a Full Site Publish as per Sitecore recommendation from the installation guide.



                    The reason why a Full Site Publish is recommended is because you'll make sure that the master and web databases are sync, i.e, items on master is present on web. I noticed that the Full Site Publish on a new Sitecore instance does not take long to run and also, I see that there are new items get created on the web database.



                    Moreover, if you have an extremely large number of changes (new instance or migrated/rewrote your entire site) the Smart Publish could also take a very long time since not only will it have to update almost all the items but it will also have to do the comparisons of each item.



                    Then, you can use incremental or smart publish afterwards. Normally, I tend to create an auto-publish agent which use the incremental publish. The job is ran every 1 hour to push changes live.






                    share|improve this answer


























                    • "because you'll make sure that the master and web databases are sync" so that means that the smart publish may result in a not synced state?

                      – Hugo Santos
                      9 hours ago











                    • Smart Publish makes use of the revision field. So, if the revision id is same, it will skip the item. But republish will assure that all items are exactly the same on the target database (not taking into consideration workflow here).

                      – Hishaam Namooya
                      9 hours ago











                    • But since we are talking about a brand new Sitecore instance, the revision ID should not cause any issue (famous last words)... Did you have experienced something different in real life?

                      – Hugo Santos
                      9 hours ago











                    • As far as i know, it should not be a problem. I’ll try to test the performance of both in the coming days and I’ll update the answer. Truly speaking i think republish and smart publish on new instance may take approximately the same amount of time as the root item for smart publish will be the sitecore item. So it will compare each item while full publish will just push the item to web

                      – Hishaam Namooya
                      9 hours ago














                    2












                    2








                    2







                    If you are creating a new Sitecore Instance, I would recommend to use a Full Site Publish as per Sitecore recommendation from the installation guide.



                    The reason why a Full Site Publish is recommended is because you'll make sure that the master and web databases are sync, i.e, items on master is present on web. I noticed that the Full Site Publish on a new Sitecore instance does not take long to run and also, I see that there are new items get created on the web database.



                    Moreover, if you have an extremely large number of changes (new instance or migrated/rewrote your entire site) the Smart Publish could also take a very long time since not only will it have to update almost all the items but it will also have to do the comparisons of each item.



                    Then, you can use incremental or smart publish afterwards. Normally, I tend to create an auto-publish agent which use the incremental publish. The job is ran every 1 hour to push changes live.






                    share|improve this answer















                    If you are creating a new Sitecore Instance, I would recommend to use a Full Site Publish as per Sitecore recommendation from the installation guide.



                    The reason why a Full Site Publish is recommended is because you'll make sure that the master and web databases are sync, i.e, items on master is present on web. I noticed that the Full Site Publish on a new Sitecore instance does not take long to run and also, I see that there are new items get created on the web database.



                    Moreover, if you have an extremely large number of changes (new instance or migrated/rewrote your entire site) the Smart Publish could also take a very long time since not only will it have to update almost all the items but it will also have to do the comparisons of each item.



                    Then, you can use incremental or smart publish afterwards. Normally, I tend to create an auto-publish agent which use the incremental publish. The job is ran every 1 hour to push changes live.







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited 9 hours ago

























                    answered 10 hours ago









                    Hishaam NamooyaHishaam Namooya

                    6,7291627




                    6,7291627













                    • "because you'll make sure that the master and web databases are sync" so that means that the smart publish may result in a not synced state?

                      – Hugo Santos
                      9 hours ago











                    • Smart Publish makes use of the revision field. So, if the revision id is same, it will skip the item. But republish will assure that all items are exactly the same on the target database (not taking into consideration workflow here).

                      – Hishaam Namooya
                      9 hours ago











                    • But since we are talking about a brand new Sitecore instance, the revision ID should not cause any issue (famous last words)... Did you have experienced something different in real life?

                      – Hugo Santos
                      9 hours ago











                    • As far as i know, it should not be a problem. I’ll try to test the performance of both in the coming days and I’ll update the answer. Truly speaking i think republish and smart publish on new instance may take approximately the same amount of time as the root item for smart publish will be the sitecore item. So it will compare each item while full publish will just push the item to web

                      – Hishaam Namooya
                      9 hours ago



















                    • "because you'll make sure that the master and web databases are sync" so that means that the smart publish may result in a not synced state?

                      – Hugo Santos
                      9 hours ago











                    • Smart Publish makes use of the revision field. So, if the revision id is same, it will skip the item. But republish will assure that all items are exactly the same on the target database (not taking into consideration workflow here).

                      – Hishaam Namooya
                      9 hours ago











                    • But since we are talking about a brand new Sitecore instance, the revision ID should not cause any issue (famous last words)... Did you have experienced something different in real life?

                      – Hugo Santos
                      9 hours ago











                    • As far as i know, it should not be a problem. I’ll try to test the performance of both in the coming days and I’ll update the answer. Truly speaking i think republish and smart publish on new instance may take approximately the same amount of time as the root item for smart publish will be the sitecore item. So it will compare each item while full publish will just push the item to web

                      – Hishaam Namooya
                      9 hours ago

















                    "because you'll make sure that the master and web databases are sync" so that means that the smart publish may result in a not synced state?

                    – Hugo Santos
                    9 hours ago





                    "because you'll make sure that the master and web databases are sync" so that means that the smart publish may result in a not synced state?

                    – Hugo Santos
                    9 hours ago













                    Smart Publish makes use of the revision field. So, if the revision id is same, it will skip the item. But republish will assure that all items are exactly the same on the target database (not taking into consideration workflow here).

                    – Hishaam Namooya
                    9 hours ago





                    Smart Publish makes use of the revision field. So, if the revision id is same, it will skip the item. But republish will assure that all items are exactly the same on the target database (not taking into consideration workflow here).

                    – Hishaam Namooya
                    9 hours ago













                    But since we are talking about a brand new Sitecore instance, the revision ID should not cause any issue (famous last words)... Did you have experienced something different in real life?

                    – Hugo Santos
                    9 hours ago





                    But since we are talking about a brand new Sitecore instance, the revision ID should not cause any issue (famous last words)... Did you have experienced something different in real life?

                    – Hugo Santos
                    9 hours ago













                    As far as i know, it should not be a problem. I’ll try to test the performance of both in the coming days and I’ll update the answer. Truly speaking i think republish and smart publish on new instance may take approximately the same amount of time as the root item for smart publish will be the sitecore item. So it will compare each item while full publish will just push the item to web

                    – Hishaam Namooya
                    9 hours ago





                    As far as i know, it should not be a problem. I’ll try to test the performance of both in the coming days and I’ll update the answer. Truly speaking i think republish and smart publish on new instance may take approximately the same amount of time as the root item for smart publish will be the sitecore item. So it will compare each item while full publish will just push the item to web

                    – Hishaam Namooya
                    9 hours ago


















                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Sitecore Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f18005%2fperform-a-smart-publish-or-republish-on-a-brand-new-sitecore-instance%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Masuk log Menu navigasi

                    Identifying “long and narrow” polygons in with PostGISlength and width of polygonWhy postgis st_overlaps reports Qgis' “avoid intersections” generated polygon as overlapping with others?Adjusting polygons to boundary and filling holesDrawing polygons with fixed area?How to remove spikes in Polygons with PostGISDeleting sliver polygons after difference operation in QGIS?Snapping boundaries in PostGISSplit polygon into parts adding attributes based on underlying polygon in QGISSplitting overlap between polygons and assign to nearest polygon using PostGIS?Expanding polygons and clipping at midpoint?Removing Intersection of Buffers in Same Layers

                    Старые Смолеговицы Содержание История | География | Демография | Достопримечательности | Примечания | НавигацияHGЯOLHGЯOL41 206 832 01641 606 406 141Административно-территориальное деление Ленинградской области«Переписная оброчная книга Водской пятины 1500 года», С. 793«Карта Ингерманландии: Ивангорода, Яма, Копорья, Нотеборга», по материалам 1676 г.«Генеральная карта провинции Ингерманландии» Э. Белинга и А. Андерсина, 1704 г., составлена по материалам 1678 г.«Географический чертёж над Ижорскою землей со своими городами» Адриана Шонбека 1705 г.Новая и достоверная всей Ингерманландии ланткарта. Грав. А. Ростовцев. СПб., 1727 г.Топографическая карта Санкт-Петербургской губернии. 5-и верстка. Шуберт. 1834 г.Описание Санкт-Петербургской губернии по уездам и станамСпецкарта западной части России Ф. Ф. Шуберта. 1844 г.Алфавитный список селений по уездам и станам С.-Петербургской губернииСписки населённых мест Российской Империи, составленные и издаваемые центральным статистическим комитетом министерства внутренних дел. XXXVII. Санкт-Петербургская губерния. По состоянию на 1862 год. СПб. 1864. С. 203Материалы по статистике народного хозяйства в С.-Петербургской губернии. Вып. IX. Частновладельческое хозяйство в Ямбургском уезде. СПб, 1888, С. 146, С. 2, 7, 54Положение о гербе муниципального образования Курское сельское поселениеСправочник истории административно-территориального деления Ленинградской области.Топографическая карта Ленинградской области, квадрат О-35-23-В (Хотыницы), 1930 г.АрхивированоАдминистративно-территориальное деление Ленинградской области. — Л., 1933, С. 27, 198АрхивированоАдминистративно-экономический справочник по Ленинградской области. — Л., 1936, с. 219АрхивированоАдминистративно-территориальное деление Ленинградской области. — Л., 1966, с. 175АрхивированоАдминистративно-территориальное деление Ленинградской области. — Лениздат, 1973, С. 180АрхивированоАдминистративно-территориальное деление Ленинградской области. — Лениздат, 1990, ISBN 5-289-00612-5, С. 38АрхивированоАдминистративно-территориальное деление Ленинградской области. — СПб., 2007, с. 60АрхивированоКоряков Юрий База данных «Этно-языковой состав населённых пунктов России». Ленинградская область.Административно-территориальное деление Ленинградской области. — СПб, 1997, ISBN 5-86153-055-6, С. 41АрхивированоКультовый комплекс Старые Смолеговицы // Электронная энциклопедия ЭрмитажаПроблемы выявления, изучения и сохранения культовых комплексов с каменными крестами: по материалам работ 2016-2017 гг. в Ленинградской области