Options

restore SQL db to native error

nikeman77nikeman77 Member Posts: 517
hi all,

i have a database with 10 companies (A1~A10)

A10 is the HQ (with the highes t number of transactions, data)

The rest of the companies A1~A9 i have no problem restore from fbk file to my native.
My local db size can only set to 62GB.

I check my LIVE database the size is 120GB (using similar licence)

Why is the LIVE (SQL) able to accomodate such a big file size while my local unable to ?
Is there anyway that I can restore to my local ? (Eg: Any compressions of data) :-k
Error:
there is not sufficient space available in the database to perform this task. You can obtain more space by:
*Expanding the database.
*Deleting the unnecessary data.
*Date compressing older, non-current entries.
*optimizing the database.
«1

Answers

  • Options
    bbrownbbrown Member Posts: 3,268
    What version is this? Is the 62 GB limit because of physical disk space? If so, get a larger drive. If it's because of a license restriction then get it expanded. Native can support up to 256 GB.

    SQL has not size restrictions. Only that of the physical system.
    There are no bugs - only undocumented features.
  • Options
    nikeman77nikeman77 Member Posts: 517
    bbrown,

    i am not so sure.. i try to restore into another sql testdb and from there do an INDIVIDUAL company (A10) backup *fbk. then follow by restore into the local ones again..
    the 256gb for native is something new to me :thumbsup:
  • Options
    bbrownbbrown Member Posts: 3,268
    Which of my questions are you not sure about?

    Look at your license. Do you see granule 1370? If so, what's the amount?

    If you have the text file for the license, look for "Maximum Database Size".
    There are no bugs - only undocumented features.
  • Options
    SavatageSavatage Member Posts: 7,142
    depends on your license - ours is 65. and since we are not on contract - i doubt we can increase it
  • Options
    bbrownbbrown Member Posts: 3,268
    A database that's been expanded to he 256 GB limit will have an entry like this in the license:
    1,370 Database Expansion per 1 GB 192

    That's the base 64 GB + 192 GB = 256 GB

    Granule 1375 will allow you to go beyond the 256 GB limit. You must specially request it and there is no support. Meaning if it fails, tough luck.
    There are no bugs - only undocumented features.
  • Options
    nikeman77nikeman77 Member Posts: 517
    bbrown wrote:
    Which of my questions are you not sure about?
    Look at your license. Do you see granule 1370? If so, what's the amount?
    If you have the text file for the license, look for "Maximum Database Size".

    I didnt see granule 1370 in my license information.
    how do i view the text file for the license.. i can only go to Tools> License information.

    A database that's been expanded to he 256 GB limit will have an entry like this in the license:
    Cant find the entry of database information expanded in my license.

    Database Used(KB) : 12,207,448 [20%]
    Database Size(KB) : 61,000,000 [93%]
    Licensed Size(KB) : 65,536,000KB
    DBMS Cache(KB) : 8000
    Object cache(KB) : 32,000
  • Options
    nikeman77nikeman77 Member Posts: 517
    Savatage wrote:
    depends on your license - ours is 65. and since we are not on contract - i doubt we can increase it
    How do I check the limitation ?
    File>Database Information ? mine would be 62GB.. 8)
  • Options
    nikeman77nikeman77 Member Posts: 517
    guys:

    worse case scenario proposition: :idea:
    create another NATIVE database (subject to the available capacity of my local physical disk ) to restore
    A10 which is the company with highest disk space.. :roll:
  • Options
    bbrownbbrown Member Posts: 3,268
    Purchase a copy of SQL Server - Developer Edition ($50) and install on your local machine. DB size issue solved.
    There are no bugs - only undocumented features.
  • Options
    bbrownbbrown Member Posts: 3,268
    nikeman77 wrote:
    Cant find the entry of database information expanded in my license.

    Licensed Size(KB) : 65,536,000KB

    It's right here. 64 GB
    There are no bugs - only undocumented features.
  • Options
    nikeman77nikeman77 Member Posts: 517
    hi bbrown,

    how will developer tool helps in the restoration to local db helps ? :-k
  • Options
    bbrownbbrown Member Posts: 3,268
    nikeman77 wrote:
    hi bbrown,

    how will developer tool helps in the restoration to local db helps ? :-k

    It's not "development tools". It's an edition of SQL Server that will run under a workstation class operating system. This would allow you to run SQL Server on your workstation and restore the database. Eliminating the need to convert to native.

    Of course, if your NAV license doesn't have the SQL granule, that could be a problem.
    There are no bugs - only undocumented features.
  • Options
    nikeman77nikeman77 Member Posts: 517
    bbrown,

    method 1: does optimizing the keys works ? [-o<

    method2: disable ALL of the g/l entry keys (since its the largest table in terms of size and records) leaving
    ONLY the primary keys (Entry No.) and continue the restore.
    Then slowly activate them one by one back.. [-o<
  • Options
    nikeman77nikeman77 Member Posts: 517
    By the way, when i restore ONLY company A10 from LIVE, the resulting fbk files is a little bit 'funny' instead of 1 fbk files,
    it produce about 15pcs of files(*.fbk) eack aprox 2GB
    ](*,)
  • Options
    bbrownbbrown Member Posts: 3,268
    nikeman77 wrote:
    By the way, when i restore ONLY company A10 from LIVE, the resulting fbk files is a little bit 'funny' instead of 1 fbk files,
    it produce about 15pcs of files(*.fbk) eack aprox 2GB
    ](*,)

    That's the correct behavior. They are exactly 2 GB each. Except the last one.
    There are no bugs - only undocumented features.
  • Options
    nikeman77nikeman77 Member Posts: 517
    [/quote]It's not "development tools". It's an edition of SQL Server that will run under a workstation class operating system. This would allow you to run SQL Server on your workstation and restore the database. Eliminating the need to convert to native.
    Of course, if your NAV license doesn't have the SQL granule, that could be a problem.[/quote]

    I have SQL Mgt Stdio (v10) installed, does it mean that I can 'Attached' my 'native' db to SQL Mgt Stdio?
    and using local pc as a storage instead of connecting it into a physical server ?

    The transaction log, primary, secondary memory will expand depending on my local pc physical memory available space?
  • Options
    bbrownbbrown Member Posts: 3,268
    SSMS is just a client tool. It's not the database engine. I'm referring SQL Server - Developer Edition. You'll need to purchase it. This edition allows you to run the database server under a worksation O/S such as WIndows 7, etc. In terms of functionality, the Developer Edition is equilavent to Enterprise.

    In terms of the files sizes, you'd be best to create them large enough in the first place.

    But first you need to have "Granule 2010 - Microsoft SQL Server Option" in your NAV license. Without it this SQL discussion is meaningless.
    There are no bugs - only undocumented features.
  • Options
    nikeman77nikeman77 Member Posts: 517
    But first you need to have "Granule 2010 - Microsoft SQL Server Option" in your NAV license. Without it this SQL discussion is meaningless.
    :)
    Yes I have in the license.
    i am able to edit new query and run it in my sql mgt stdio does it mean i have the developing license/ version ?
    How do i tell if i have a developing license.. sorry i am a newbie in SQL..
  • Options
    bbrownbbrown Member Posts: 3,268
    In the left panel in SSMS, right-click the server name and choose Properties. WHat does it say under Product on the General tab?
    There are no bugs - only undocumented features.
  • Options
    nikeman77nikeman77 Member Posts: 517
    bbrown wrote:
    In the left panel in SSMS, right-click the server name and choose Properties. WHat does it say under Product on the General tab?
    It says: Microsoft SQL Server Enterprise Edition
    :(
  • Options
    nikeman77nikeman77 Member Posts: 517
    version 10.0.2531.0
  • Options
    bbrownbbrown Member Posts: 3,268
    Are you sure management studio isn't connecting to a server somewhere on your network? Makes not sense that Enterprise Edition would be installed on your local computer. Of course, you could restore it there.

    What version of WIndows is your local computer running?
    There are no bugs - only undocumented features.
  • Options
    bbrownbbrown Member Posts: 3,268
    Totally different question:

    WHy don't you just use the same license from the live database? That obviously supports the larger DB.
    There are no bugs - only undocumented features.
  • Options
    nikeman77nikeman77 Member Posts: 517
    Are you sure management studio isn't connecting to a server somewhere on your network?
    Yes its connected.
    Makes not sense that Enterprise Edition would be installed on your local computer. Of course, you could restore it there.
    its a server where we remote into the workstation, and thats where SQL Enterprise Edition is installed. Also thats where I restored my local navision. Where I can only
    access it locally.
    What version of WIndows is your local computer running?
    Microsoft Windows Server 2003
  • Options
    nikeman77nikeman77 Member Posts: 517
    bbrown wrote:
    Totally different question:
    WHy don't you just use the same license from the live database? That obviously supports the larger DB.
    :-k

    License is the same, but LIVE version is FinSql.exe, myrestored version is Fin.exe :roll:
  • Options
    bbrownbbrown Member Posts: 3,268
    Your local computer is running "Microsoft Windows Server 2003"?
    There are no bugs - only undocumented features.
  • Options
    bbrownbbrown Member Posts: 3,268
    nikeman77 wrote:
    bbrown wrote:
    Totally different question:
    WHy don't you just use the same license from the live database? That obviously supports the larger DB.
    :-k

    License is the same, but LIVE version is FinSql.exe, myrestored version is Fin.exe :roll:


    Restore to SQL and use FINSQL.EXE
    There are no bugs - only undocumented features.
  • Options
    nikeman77nikeman77 Member Posts: 517
    Your local computer is running "Microsoft Windows Server 2003"?
    its a server where we remote into the workstation, and thats where SQL Enterprise Edition is installed. Also thats where I restored my local navision. Where I can only
    access it locally.
  • Options
    nikeman77nikeman77 Member Posts: 517
    bbrown wrote:
    Restore to SQL and use FINSQL.EXE
    it will not be native anymore... :(
  • Options
    bbrownbbrown Member Posts: 3,268
    nikeman77 wrote:
    bbrown wrote:
    Restore to SQL and use FINSQL.EXE
    it will not be native anymore... :(

    That's the idea. Why do you want to run native if the live DB is SQL?
    There are no bugs - only undocumented features.
Sign In or Register to comment.