Community
Command Central
MVP Program
Monthly Mission
Blogs
Groups
Events
Media Vault
Products
Observability
Network Management
Application Management
IT Security
IT Service Management
System Management
Database Management
Content Exchange
SolarWinds Platform
Server & Application Monitor
Database Performance Analyzer
Server Configuration Monitor
Network Performance Monitor
Network Configuration Manager
SQL Sentry
Web Help Desk
Free Tools & Trials
Store
Home
Products
Network Performance Monitor (NPM)
database maintenance
cindy
What is the procedure for archiving data from the sql database? For example, the documentation says that the max size is 2GB. After compacting and stuff, what happens when the database is close to the 2Gb? How do you export that data and save it to tape or something. We will possibly be required to keep a few years worth of performance statistics.... And then, on the flip side, how do you look at that
archived data??? Sorry if this is a dumb question - maybe I'm just missing something???
Thanks
C.
Find more posts tagged with
Accepted answers
All comments
iunderwo
Once the database starts to near 2gb, SW will raise a critical alert to let you know it's getting full. After the limit is reached, no new data will actually get inserted, resulting in a timespan of lost data until some room is recovered. Exporting data itself isn't too difficult, but putting it all togethere into something useful afterwards could pose a challenge.
Depending on the budget you can allocate for this, I'd recommend upgrading to a non-desktop version of SQL server. If you need to do any trending or analysis of the data, you'll need the larger DB size.
The 2gb limit isn't determined by SolarWinds, but rather the Microsoft backend. SQL 2005 Express will get you up to 4gb.
// Ian Underwood - Network Engineering
// Boston Stock Exchange
Quick Links
All Categories
Recent Posts
Activity
Unanswered
Groups
Help
Best Of