Local database deployment problems and fixtures
2014-11-07 20:03
676 查看
/*By Jiangong SUN*/
After encountering some problems in deploying databases to local server, here are some tips which could be helpful in the database deployment exercises.
When you deploy your databases. You can monitor the progress in "Data Tools Operations" view.
The deployment can have all the following steps:
Step 1. Creating publish preview
Step 2. Creating database script
Step 3. Executing publish script on database 'Your database'.
Step 4. Publish completed successfully
In my experience, the failure in Step 1 could happen when you generate the database script.
If you have this problem, build the project and retry.
In Step 2 you could meet a problem like : the script file could not be found
In this case, just locate your project folder and find the file "{DB_Name}.dbmdl" and delete it. Then retry.
In other cases, if the database script is correctly generated and there is a problem, you can even execute and debug the script "{DB_Name}_{Publish_Number}.publish.sql".
If you meet the problem at Step 3, you can click on "View Results" to locate where the problem is.
If you can't locate the problem, just debug the generated SQL script.
I hope this post can do help to you!!!
Enjoy coding!
After encountering some problems in deploying databases to local server, here are some tips which could be helpful in the database deployment exercises.
When you deploy your databases. You can monitor the progress in "Data Tools Operations" view.
The deployment can have all the following steps:
Step 1. Creating publish preview
Step 2. Creating database script
Step 3. Executing publish script on database 'Your database'.
Step 4. Publish completed successfully
In my experience, the failure in Step 1 could happen when you generate the database script.
If you have this problem, build the project and retry.
In Step 2 you could meet a problem like : the script file could not be found
In this case, just locate your project folder and find the file "{DB_Name}.dbmdl" and delete it. Then retry.
In other cases, if the database script is correctly generated and there is a problem, you can even execute and debug the script "{DB_Name}_{Publish_Number}.publish.sql".
If you meet the problem at Step 3, you can click on "View Results" to locate where the problem is.
If you can't locate the problem, just debug the generated SQL script.
I hope this post can do help to you!!!
Enjoy coding!
相关文章推荐
- Local database deployment problems and fixtures
- Step by step Install a Local Report Server and Remote Report Server Database
- Install_Oracle_Database_11g on RedHat 6.4 – problems and solution
- VCM tips: jar deployment path/install default user name and password/Oracle database schema clean/VPD file clean
- The database has local access protection and you are not authorized to access it locally
- export out remote database and inport into local database
- How to set up ADB for remote machine development and local device deployment
- ASP.NET Deployment and Configuration Problems
- Steps To Migrate-Move a Database From Non-ASM to ASM And Vice-Versa
- Some ebooks Linux, Java, .NET, Network and database
- First ModalPopupExtender example and some problems I run into
- Understanding the Local Service and Network Service Accounts
- Machine Learning and Database
- ArcGIS Server Help 之 Geodatabase and ArcSDE 学习笔记
- 第 15 & 16 章 Jenkins –Automated Deployment&Metrics and Trends
- Problems and Opportunities
- 评论数据库Win A Free Copy of Packt’s Managing Multimedia and Unstructured Data in the Oracle Database e-book
- A clojure DSL for system admin and deployment with many remote machines
- Cost Based Optimizer (CBO) and Database Statistics
- Error occurred in deployment step 'Activate Features': Feature with Id '{GUID}' is not installed in this farm, and cannot be added to this scope.