VStudio中的并发SQLServer和App开发 [英] Concurrent SQLServer and App Developement within VStudio
问题描述
不是编程新手，但对VStudio和SQL Server不熟悉。我正在从Access DB到SQL Server的步骤。我正在寻找一种策略来开发我的SQLServer数据库（表等），同时还在开发我的应用程序，这些应用程序将被分发以在visual studio中访问它，并且希望能够在VStudio界面中工作以完成所有工作。这是场景：
1.需要能够在多个内部和外部的开发机器上访问最终SQL Server DB的本地开发副本我们的工作团队。
2.我希望能够使用与最终安装的客户端应用程序类似的连接方法连接到本地副本。我知道连接字符串最终会改变
3.数据库的本地开发副本最终会部署到我们公司范围的SQL服务器上。
我对一些''最佳实践'感兴趣。我一直在本地机器上试验.mdf文件和SQLExpress，但我没有在各种开发机器上获得可重现的结果。我也发现为每台开发机器安装和配置SQLExpress都很费时。
似乎有几种方法可能有效，但我只是havn找不到符合我情景的那个。
任何帮助都会受到赞赏。
< blockquote> 1）不要使用Microsoft从Access到SQL的转换，或者至少确保发生了什么。我们有浮动的邮政编码，因为进行转换的人不知道他们在做什么。他们不在了。
2）想想三层实施。至少一个开发SQL实例，一个用户测试SQL实例和一个生产实例。任何您授予权限的人都可以访问SQL服务器。因此，您关于团队外部人员能够访问开发系统的问题是部分网络和部分SQL安全性。
3）考虑如何使所有内容保持同步。可以更改开发服务器上的数据以进行测试。开发人员可能需要当前数据来测试问题。
4）开发良好的备份和恢复。
祝你好运。我希望这至少可以给你一个起点，或者激发一个想法。
Not new to programming, but am new to VStudio and SQL Server. I''m taking the step from Access DB''s to SQL Server. I''m looking for a strategy to develop my SQLServer DB (tables etc) while also working on developing my application that will be distributed to access it in visual studio and would like to be able to work within the VStudio interface for all our efforts. Here''s the scenario:
1. Need to be able to access a local development copy of the eventual SQL server DB on multiple development machines both inside and outside of our working team.
2. I would like to be able to connect to the local copy using connection methods that would be similar to the final installed client application. I know that the connections strings will change eventually
3. The local development copy of the DB would eventually be deployed to our company wide SQL server.
I''m interested in some ''best practices''. I''ve been experimenting with .mdf files and SQLExpress on local machines but i''m not getting reproducable results on various development machines. I''m also finding it time consuming to install and configure SQLExpress suitably for each development machine.
There seems to be several methods that could possibly work but I simply havn''t found the one yet that would fit my scenario.
Any help would be appreciated.
1) Do not use Microsoft''s convert from Access to SQL, or at least make sure what is happening. We have zip codes that are float because the person who did the conversion did not know what they were doing. They are no longer here.
2) Think about a three tier implementation. At lest one Development SQL instance, one user test SQL instance, and one production instance. A SQL server may be accessed by anyone you give permissions to. Thus your question about people outside your team being able to access the development system is part network and part SQL security.
3) Think about how to keep everything in sync. Data on the development server may be changed for a test. The developer may need current data to test a problem.
4) Develop a good backup and recovery.
Good luck. I hope this at least gives you a starting point, or sparks an idea.
这篇关于VStudio中的并发SQLServer和App开发的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
