Using the default SQL Server instance for Windows Azure development storage
2012-04-17 22:57
429 查看
http://www.wadewegner.com/2010/07/using-the-default-sql-server-instance-for-windows-azure-development-storage/
This tip isn’t new, but it’s still useful. I found myself building a new development box this week, and I didn’t want to use SQLExpress for the Windows Azure development storage. Instead, I wanted
to use the default instance for SQL Server.
It’s pretty simple to do this – after you install the Windows Azure SDK and Tools, go to a command prompt and browse to the following folder:C:Program FilesWindows Azure SDKv1.2bindevstore (or wherever
you installed the SDK). From there, use the DSInit.exe tool:
Remember that the . is a reference to the default instance. If you want to target an instance name, you can use:
Note: from riverlau
In SDK v1.6, the
DSInit.exe path is changed to "C:\Program Files\Windows Azure Emulator\emulator\devstore\DSInit.exe"
This tip isn’t new, but it’s still useful. I found myself building a new development box this week, and I didn’t want to use SQLExpress for the Windows Azure development storage. Instead, I wanted
to use the default instance for SQL Server.
It’s pretty simple to do this – after you install the Windows Azure SDK and Tools, go to a command prompt and browse to the following folder:C:Program FilesWindows Azure SDKv1.2bindevstore (or wherever
you installed the SDK). From there, use the DSInit.exe tool:
DSInit.exe /sqlInstance:.
Remember that the . is a reference to the default instance. If you want to target an instance name, you can use:
DSInit.exe /sqlInstance:YourInstanceName
Note: from riverlau
In SDK v1.6, the
DSInit.exe path is changed to "C:\Program Files\Windows Azure Emulator\emulator\devstore\DSInit.exe"
相关文章推荐
- Default SQL Server instance for the local Development Storage
- Default SQL Server instance for the local Development Storage
- 配置SQL Server Instance for Azure Development Storage
- 解决Azure “Failed to start Storage Emulator: the SQL Server instance `.\' could not be found.”
- Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection
- Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection
- [转]Using the Microsoft Connector for Oracle by Attunity with SQL Server 2008 Integration Services
- Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection
- Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection
- Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection
- dbvis MySQL server version for the right syntax to use near 'OPTION SQL_SELECT_LIMIT=DEFAULT' at lin
- Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance
- Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
- MySQL server version for the right syntax to use near 'OPTION SQL_SELECT_LIMIT=DEFAULT’
- using sql server or sql azure for session state store in asp.net
- Designing Data Storage Architecture-Using the Windows Azure Storage Services
- MS SQL错误:SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems
- dbvis MySQL server version for the right syntax to use near 'OPTION SQL_SELECT_LIMIT=DEFAULT' at lin
- MySQL server version for the right syntax to use near 'OPTION SQL_SELECT_LIMIT=DEFAULT' at line 1
- sql express 2008 - Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instan