SQL 2008 Developer以SQL Azure迁移 [英] Sql 2008 Developer to Sql Azure Migration
问题描述
大家好，我公司决定对现有的应用程序切换到Azure平台（仅SQL语句组成部分）。因此，我们需要从本地上传我们的数据库云。对于迁移我碰到喜欢的各种工具
1. cerebrata的工具
2. SqlAzure迁移向导
3.微软SQL数据同步
4.通过管理工作室传统的脚本方式。
但是，所有的上述工具表明，他们有能力有限。用户不能在任一工具的工作得很好。
Hi My company is deciding for switching its existing application to azure platform (only Sql Part). So we need to upload our db from local to cloud. For migration i came across various tools like 1. cerebrata 's tools 2. SqlAzure Migration wizard 3. Microsoft Sql Data Sync 4. Conventional Script way via management studio. But all the above tools showed that they have limited capacity. A user cannot work flawlessly on either of the tool.
-
在cerebrata的工具 - 的主要缺点是其应用程序的用户名和应用的关键领域，我还没有管理共享。此外还有Azure和地方之间的字段手动映射。
In cerebrata's tool - the main drawback was its field for Application User Name and Application Key , which my admin havent shared. Also there is manual mapping of fields between azure and local.
的Sql Azure迁移向导 - 生成脚本和执行，但也有很多的错误。我用它的2.1版本。此外，它很慢。看来，它的SQL SRVR管理工作室的翻版。
Sql Azure Migration wizard - generates scripts and executed too but with lots of error . I was using its version 2.1. Also it very slow. It seems that its a replica of Sql Srvr Mgmt Studio.
SQL数据同步： - 我发现它很酷作为一个MS的产品，但它有局限性太大，它仅使用Windows身份验证基于本地SQL Server连接，或者您需要明确允许必需的，但。即使考虑而同步后，我得到了一些SQL Azure的部署错误。
Sql Data Sync :- I found it cool as its a MS product but it has limitation too that it only connects with Windows Authentication based local sql server, or you need to explicitly allow the required but. Even after allowing while syncing , I got some Sql Azure Provisioning Error.
4的Sql SRVR管理工作室： - 这是最简单的方法，但需要大量的手工操作的实际迁移之前做。我所做的是我整个生成数据库的脚本（单DB近101123行code），并试图在Azure上运行。在我第一次遇到了一些关键字匹配错误。最后我删除主键声明毕竟行随着（填充=关....）或相似，也未尝初级然后我执行，但仍对设置标识插入在遇到错误。在去除做了很多艰苦的工作后，多余的线条等待超过2小时，以完成了剧本远程，我没有错误，错误和错误。
4 Sql Srvr Mgmt Studio :- This is most easiest way but requires a lot of manual work to do before actual migration. What i did is that I generated a script of entire db (almost 101123 lines of code for single db) and tried to execute on azure. On the very first time i faced some keyword mismatch error . Finally i removed all line after primary key declaration that With (Padding = Off ....)or something similar and also On Primary then i executed , but still got error on Set Identity Insert On. After doing a lot of hard work in removing unwanted lines waited more than 2 hrs to completed the script remotely, i got no Errors , errors and errors.
所以，请你们来取悦建议我比上述任何好的替代方案就是我缺了点什么，可以做更多的上方。
So you guys are requested to please suggest me any good alternative stated than above or i am lacking something and can do more with above.
感谢
阿米特兰詹
推荐答案
我最近遇到了类似的问题，通过运行你所列出的选项。
I've faced a similar problem recently, running through the options you've listed.
您可能会给一个尝试红门测试版的Azure （自由几个月）。我发现他们的工具是SQL架构和数据复制相当不错。
You might give a try to Red-Gate beta for Azure (free for a few months). I found their tools to be quite good for SQL schema and data replication.
没试过在Azure自己建，但（我手动迁移表由我被告知报价的时间）。
Never tried the Azure build myself, though (I migrated tables manually by the time I was told about the offer).
这篇关于SQL 2008 Developer以SQL Azure迁移的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
