0

I have a .net application using sql server 2005 database. This is a very simple data entry application. But the client is using it for a very long time and speed of the application getting worst with the time as the size of database is growing.

Client is not ready to delete the previos data from the database but want to versioning it in different database so they could use it if they want it later and speed issue will also resolved as the actual database move old data to a different database.

So kindly guide me in the right direction to achieve this.

Partition table looks very effective way to solve the issue and after doing every if & else, i come to know that this is not available in express edition of sql server. Help me, i am even ready to move the db to sql server 2008 express edition for this feature, but this option is not available in sql 2008 express as well. Kindly suggest me some workaround around free sql server editions

Thanks

Improve this question
1

1 Answer 1

Reset to default
1

Question is possibly slightly off-topic, but I suggest rebuilding your indexes (assuming you have them, otherwise that's a different matter...) and ensuring your statistics are up to date.

Craate a regular maintenance task to do this.

Also, ensure you do not have any cursor based code that is giving you O(N^2) behaviour...

Improve this answer
Sign up to request clarification or add additional context in comments.

1 Comment

Agree, check index fragmentation levels. We once employed a DBA that didn't do this...

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.