SQL Server Transactional Log (LDF) files having a 2 TB limit‏.... naaa

Discussion SQL Server Transactional Log (LDF) files having a 2 TB limit‏.... naaa

ตอบทั้งหมด

  • 13 กรกฎาคม 2555 16:23
     
     
    How many log file your database is having ? 2.7 TB is the size of single log file or the consolidate size of all ldf file size of database.

    Please click the Mark as Answer or Vote As Helpful if a post solves your problem or is helpful!


  • 13 กรกฎาคม 2555 23:16
     
     
    How many log file your database is having ? 2.7 TB is the size of single log file or the consolidate size of all ldf file size of database.

    Please click the Mark as Answer or Vote As Helpful if a post solves your problem or is helpful!

    Please see the attachments in the connect link above.

    yup

  • 19 กรกฎาคม 2555 4:37
     
     
  • 25 กรกฎาคม 2555 5:04
     
     
    I guess the key word here is "supported". I.e., only 2 GB is supported, even though it is possile to create bigger files.

    Tibor Karaszi, SQL Server MVP | web | blog

  • 25 กรกฎาคม 2555 10:50
     
     
    I guess the key word here is "supported". I.e., only 2 GB is supported, even though it is possile to create bigger files.

    Tibor Karaszi, SQL Server MVP | web | blog

    Again I'll presume yours as a typu above.... "2 GB", what MS says "officially saying we support log files to  TB." they did the typo too... but atleast this calls for a correction in BOL where the LDF limitations are quoted a 2 TB.


    yup


    • แก้ไขโดย yup. _ 25 กรกฎาคม 2555 10:50
    •  
  • 25 กรกฎาคม 2555 12:20
     
     

    Yes, that was a typo, I meant 2 TB, not 2 GB. I don't understand what you mean by below though:

    "but atleast this calls for a correction in BOL where the LDF limitations are quoted a 2 TB."

    But the supported max for LDF *is* 2 TB, not 2.7 TB. The fact that you can make it 2.7 TB doesn't mean that size is supported. Similar to number of instances. You can install more than 50 instances, but only 50 is supported.

    What could be argued is that SQL Server should limit the size, so we don't by mistake go over the supported size. That is a different thing from a documentation bug. That would be a functionality request/enhancement. Similar to if the setup program would prohibit us from installing more than 50 instances.


    Tibor Karaszi, SQL Server MVP | web | blog

  • 25 กรกฎาคม 2555 15:58
     
     

    This will be a repeat, if you look at this page here http://msdn.microsoft.com/en-us/library/ms143432 it lists the kind of limitations (Maximum Capacity Specifications for SQL Server) like Databases per instance of SQL Server, Nonclustered indexes per table, Clustered indexes per table and so on....

    No where any thing is stated as a supported count.... there is a difference between whats supported by MS & whats available/possible with the tool (in this case SQL Server).

    If you will take a look at this page here http://technet.microsoft.com/en-us/library/ms176061 which states "log file specified with unlimited growth has a maximum size of 2 TB, and a data file has a maximum size of 16 TB". Now those lines should be modified for exceptions or something like a tested to this extent only. Just to avoid any wrong concepts like you may see here http://www.sqlservercentral.com/Forums/Topic1270510-1550-3.aspx#bm1329840.

    Those first 2 links there make it look like a LDF is capped to 2 TB which is not true again its a fact that no one will have an LDF puched to this limit but atleast the pages from MS should state that with a reason.


    yup

  • 3 สิงหาคม 2555 3:13
     
     

    Similar to number of instances. You can install more than 50 instances, but only 50 is supported.

    Similar to if the setup program would prohibit us from installing more than 50 instances.


    Tibor Karaszi, SQL Server MVP | web | blog

    @Tibor - quoting a few lines extracted from your reply above. Have you practically checked the instance count ?

    yup

  • 21 พฤษภาคม 2556 9:10
     
     

    Checked this today on SQL 2012 sp1.

    Its now capped at 2 TB.


    yup