I've written a small application that uses a Microsoft Sql Server 2000 Database and Here lately i've been experiencing alot of performance problems with timeouts and data just taking too long to retreive. I was wondering what could i do to help with this.
Details:
My Program i wrote simply takes windows eventlogs and uploads them into a central database in general , i have also build a small asp.net page, where users could write out queries or save them for later use. The program is hitting our servers and it grabs them remotely, inserts into sql one by one, and clears out the logs when finished, it runs one a day, and generates about 12,000 events daily. (mostly login's and logoffs). once it starts it'll take about 2 and a half hours to finish going through everything.
Database Design...
Single Table, about 3.5 million rows now, takes up about 3 gigs of harddrive space.
Column Definitions
Name, Data Type
- EventEntryID INT PrimaryKey(Clustered) (Auto-Increment Identity)
- Log varchar(300)
- Type varchar(300)
- Date smalldatetime
- Source varchar(300)
- Category varchar(300)
- Message varchar(8000)
- EventID varchar(300)
- UserName varchar(300)
- Computer varchar(300)
Computer Specs:
OS: Window Server 2003
Processor: Intel 700 MHz
RAM: 1 GB
I know it's a small server, but this is pretty much the largest thing this server deals with
I've tried to monitor sql with perfmon and sql performance counters and I just don't see much of anything going wrong with it there, so i'm thinking the the hardware isn't an issue, but then again, i'm not very familar with sql.