Database overload question
|
Logged in as: Guest
|
|
Users viewing this topic:
none
|
|
Login  | |
|
Database overload question - 10.Sep.2008 10:57:40 PM
|
|
|
akozadaev
Posts: 7
Score: 0
Joined: 3.Jul.2007
Status: offline
|
Hello,
In scheduler, I created 2 jobs: export to file and delete data. Although GFI notifies that these jobs get finished successfully everytime, the database got overloaded with resulted in loosing some of the logs.
Please tell me what do I do wrong? The database size is about 300Gb already and so far all my efforts to release some free space were not successful.
Another question: assume I managed to free this database - may I go though SQL server enterprice manager and shrink the database as I want it to be smaller. Up to know I had to include additional database files in order to keep the system working - now I must do something about it as there is no way to increase the database size.
Kind Regard,
Alex
|
|
|
|
|
RE: Database overload question - 11.Sep.2008 9:38:15 AM
|
|
|
chriscsc
Posts: 4
Score: 0
Joined: 6.Dec.2007
Status: offline
|
Having the same issue. Cannot seem to free up space unless a dbcc shrink is done after moving the data to the backup dbase. However, now GFI fails to collect any events. If i find a solution before GFI gets back to you I'll post it.
|
|
|
|
|
RE: Database overload question - 11.Sep.2008 9:53:48 AM
|
|
|
DrewE
Posts: 476
Score: 0
Joined: 28.Apr.2008
From: Cary, NC
Status: offline
|
The first time GFI deletes a large amount of data from the SQL database you may need to run SQL's shrink command. Your database grows to meet the size of the data inside of it. We can move information between databases, and remove information from databases, however the database growth has already occured. Nothing within our software instructs the database to shrink. This is where the SQL shrink command would need to be used.
Typically, once GFI gets into a routine of deleteing older events and moving more events in the databases, the shrink command is no longer necessary. Again, you may find the shrink command necessary if you are setting up a maintenance job for the first time.
Also, it is recommended that you check the SQL recovery model within SQL Enterprise Manager or SQL Studio. Please ensure this is set to simple as this can cause a lot of trouble.
When indicating you have a large database, please also indicate if the MDF or LDF file is large. This will help us identify the problem quickly.
_____________________________
Drew Easley - Technical Support Representative
GFI Software - www.gfi.com
|
|
|
|
|
RE: Database overload question - 11.Sep.2008 10:15:07 AM
|
|
|
chriscsc
Posts: 4
Score: 0
Joined: 6.Dec.2007
Status: offline
|
LDF Files are fine. MDF for my installation average about 85 GIG for both main and backup.
|
|
|
|
|
RE: Database overload question - 11.Sep.2008 10:25:39 PM
|
|
|
akozadaev
Posts: 7
Score: 0
Joined: 3.Jul.2007
Status: offline
|
quote:
have a large database, please also indicate if the MDF or LDF file is large. This will help us identify the
I have the same - I have 2 MDF files 150Gb each. LDFs are not big.
|
|
|
|
|
RE: Database overload question - 12.Sep.2008 8:56:55 AM
|
|
|
DrewE
Posts: 476
Score: 0
Joined: 28.Apr.2008
From: Cary, NC
Status: offline
|
After you setup the maintenance jobs, (1) Do they complete successfully, and (2) Can you run SQL's shrink command and see a noticeable difference in your MDF size?
_____________________________
Drew Easley - Technical Support Representative
GFI Software - www.gfi.com
|
|
|
|
|
RE: Database overload question - 15.Sep.2008 12:34:51 AM
|
|
|
akozadaev
Posts: 7
Score: 0
Joined: 3.Jul.2007
Status: offline
|
quote:
ORIGINAL: DrewE
After you setup the maintenance jobs, (1) Do they complete successfully, and (2) Can you run SQL's shrink command and see a noticeable difference in your MDF size?
The maintenance jobs are as follows:
Move data older than 100 days to file. (The database contains data for more than a year)
Delete data older than 90 days. (although reports success, but old records seem to be untouched).
Maintenance jobs are always successful, however I cannot see a significant change in the database free space and consequently file size do not change after database shrink (Compress and Shink the free space scenario).
< Message edited by akozadaev -- 15.Sep.2008 1:05:25 AM >
|
|
|
|
|
RE: Database overload question - 15.Sep.2008 12:34:55 AM
|
|
|
akozadaev
Posts: 7
Score: 0
Joined: 3.Jul.2007
Status: offline
|
quote:
ORIGINAL: DrewE
After you setup the maintenance jobs, (1) Do they complete successfully, and (2) Can you run SQL's shrink command and see a noticeable difference in your MDF size?
The maintenance jobs are as follows:
Move data older than 100 days to file. (The database contains data for more than a year)
Delete data older than 90 days. (although reports success, but old records seem to be untouched).
Maintenance jobs are always successful, however I cannot see a significant change in the database free space and consequently file size do not change after database shrink (Compress and Shink the free space scenario).
< Message edited by akozadaev -- 15.Sep.2008 1:06:33 AM >
|
|
|
|
|
RE: Database overload question - 17.Sep.2008 9:09:24 AM
|
|
|
DrewE
Posts: 476
Score: 0
Joined: 28.Apr.2008
From: Cary, NC
Status: offline
|
Would you please open a support ticket at http://support.gfi.com so we can best assist you?
_____________________________
Drew Easley - Technical Support Representative
GFI Software - www.gfi.com
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
Printable Version
