Dear concern
I m using NAV 4.0 SP3 SQL DB.I m taking Backup,i want while taking backup through Navision, data of 1 table (say,Table ID 405) should not come in Backup.Can we do this.Is it possible guys?
Not out-of-the-box.
Actually you need to move the separated tables into a new Filegroup; then you could create FG Backups, excluding the tables/FG you don't want to save.
But caution: depending on the tables you skip, you might jeopardize the data-integrity in case of a restore of such an "incomplete" backup!
Not out-of-the-box.
Actually you need to move the separated tables into a new Filegroup; then you could create FG Backups, excluding the tables/FG you don't want to save.
But caution: depending on the tables you skip, you might jeopardize the data-integrity in case of a restore of such an "incomplete" backup!
How can I move the separated tables into a new Filegroup, and what do u mena by FG Backups.How can I take these backups?
Again, technically this is possible, but practically not recommended. In cases of T405 "Change Log Entry" this is probably pretty fail-safe, but with other tables you might raise a problem.
The general proceeding could be like this (all to be done in Management Studio using TSQL):
- Create new FG and DB file in new FG
- DROP all Non-Clustered Indexes (NCI)
- DROP Clustered Index (CI) using the MOVE TO clause to move the data into the new FG
- re-CREATE all in NCI in new FG
Then you could create FG Backups, only saving FGG "PRIMARY" and "Data Filegroup 1"
You could copy your database, delete all data in table 405 in the copied database and make a backup. But that's only a one time solution, not for daily backups. And as mentioned this doesn't work or is very risky for other tables.
"Money is likewise the greatest chance and the greatest scourge of mankind."
If this is not a one-time task then instead of skipping the table during backup, you could simply empty it. If you have permissions to do that, and you don't want to keep the information then why keep it? Empty it and set it up correctly so that it doesn't store too much info (if your problem is the number of entries).
Indeed! Just a good guess:
They are logging way too much, this "Change Log Entry" is a sort of "table monster", wasting precious disk-space, also with the backups.
Just this week I've worked on a database of 17GB net size; and alone T405 used 8GB!
So I agree, the preferred steps should be:
- review the Change Log setup; only logging what's really necessary
- delete old data periodically
I hesitate to suggest this, but change log is one of those tables that it's possible to put into 'DataPerCompany=No' . If it's not in a company they it won't be saved in a company backup ...
Dear concern
I m using NAV 4.0 SP3 SQL DB.I m taking Backup,i want while taking backup through Navision, data of 1 table (say,Table ID 405) should not come in Backup.Can we do this.Is it possible guys?
Comments
Actually you need to move the separated tables into a new Filegroup; then you could create FG Backups, excluding the tables/FG you don't want to save.
But caution: depending on the tables you skip, you might jeopardize the data-integrity in case of a restore of such an "incomplete" backup!
NAV/SQL Performance Optimization & Troubleshooting
STRYK System Improvement
The Blog - The Book - The Tool
How can I move the separated tables into a new Filegroup, and what do u mena by FG Backups.How can I take these backups?
Navision Technical Consultant
The general proceeding could be like this (all to be done in Management Studio using TSQL):
- Create new FG and DB file in new FG
- DROP all Non-Clustered Indexes (NCI)
- DROP Clustered Index (CI) using the MOVE TO clause to move the data into the new FG
- re-CREATE all in NCI in new FG
Then you could create FG Backups, only saving FGG "PRIMARY" and "Data Filegroup 1"
See SQL Server "Books Online" about details.
NAV/SQL Performance Optimization & Troubleshooting
STRYK System Improvement
The Blog - The Book - The Tool
Navision Technical Consultant
No, not a chance with C/SIDE Server.
NAV/SQL Performance Optimization & Troubleshooting
STRYK System Improvement
The Blog - The Book - The Tool
If this is not a one-time task then instead of skipping the table during backup, you could simply empty it. If you have permissions to do that, and you don't want to keep the information then why keep it? Empty it and set it up correctly so that it doesn't store too much info (if your problem is the number of entries).
Indeed! Just a good guess:
They are logging way too much, this "Change Log Entry" is a sort of "table monster", wasting precious disk-space, also with the backups.
Just this week I've worked on a database of 17GB net size; and alone T405 used 8GB!
So I agree, the preferred steps should be:
- review the Change Log setup; only logging what's really necessary
- delete old data periodically
NAV/SQL Performance Optimization & Troubleshooting
STRYK System Improvement
The Blog - The Book - The Tool
Just saying.
TVision Technology Ltd
Take a look at report 510 it does what you need.