views:

263

answers:

2

Hello all, we run since 2 years a small application on SQL Server 2005 Express Edition the Database has gown from 75 MB up to nearly 400MB within this time, the there isn't a big amount of data.

But the log file has been arrived at 3,7GB now without changing Hardware, table structure or Program code we noted that the Import processes which required 10-15 minutes are now arrived at a couple of hours.

any idea where could be the Problem? Depends it on the log file may be? The 4GB Lock of Express Edition bear only on data files or also on log files?

Additional Informations: There isn't any RAID on the DB Server, There doesn't work concurrent users (only one user is logged in while the import process).

Thanks in Advance Johannes

+1  A: 

From MSDN:

"The 4 GB database size limit applies only to data files and not to log files. "

SQL Server Express is also limited in that it can only use 1 processor and 1GB of memory. Have you tried monitoring the processor/memory usage while the import is running to see if this is causing a bottleneck?

Adam
+3  A: 

That the log file is so large is completely normal behavior; in the two years you have been running; sql has been keeping track of the events that happen in the database as it goes along its business.

Normally you might clear these logs off when you take a backup (as you most likely dont need them anyway.) If you are backing up all you need to change the sql script to checkpoint the logfile (its in books online) depending on how you are backing up your milage may vary.

To clear it down in the immediate make sure no one is in using the database; open management studio express find the database and run

backup log database_name with truncate_only
go
dbcc shrinkdatabase('database_name')
u07ch
Thanks for your answer yes also I am not amazed about the log file size, but about the strongly broken performance and I thought may be it is related to the log file size but also after shrinking the Log the Performance Problems does exist.
john84
The 4GB limit does not include the log file which is why shrinking it will not have helped.
Adam
If you can run a query from your application manually; try running it in management studio with the show actual execution plan enabled. After 2 years it might be fragmentation in the indexes or just that you now need indexes. The execution plan should tell you or point you in thr direction in The query as to what is slow. if its indexes need updating then you can reindex easily EXEC sp_msForEachTable @COMMAND1= 'DBCC DBREINDEX ( "?")'goEXEC sp_msForEachTable @COMMAND1= 'DBCC indexdefrag (<your_databasename>, "?")'
u07ch
If its statistics you should get the option to fix; if indices are missing then you will have to work out the best indices for your job i am afraid.
u07ch