简体   繁体   English

SQL数据库和.net应用程序的版本控制

[英]Versioning of SQL database and .net applications

I have a .net application using sql server 2005 database. 我有一个使用sql server 2005数据库的.net应用程序。 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. 客户端尚未准备好从数据库中删除previos数据,但希望在其他数据库中对其进行版本控制,以便他们以后可以使用它,并且在实际数据库将旧数据移至其他数据库时,速度问题也将得到解决。

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. 分区表看起来是解决该问题的非常有效的方法,并且在完成每一个if&else之后,我知道这在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. 帮帮我,我甚至准备为此功能将数据库移至sql server 2008 express版本,但是此选项在sql 2008 express中也不可用。 Kindly suggest me some workaround around free sql server editions 请建议我一些有关免费SQL Server版本的解决方法

Thanks 谢谢

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... 另外,请确保没有任何基于游标的代码可以给您O(N ^ 2)行为...

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM