Sign in or 

|
jberschling |
SQL db management
Mar 10 2010, 11:44 AM EST
In converting historical data (hourly and aux), I seem to have created a huge database (on the order of 30 GB?) Is it not the intention to have all data stored in one place? I see there is a SQL function "shrink database" or "shrink files" - is this recommended?
Do you find this valuable?
Keyword tags:
None
|