Difference between revisions of "SQL Azure Setup"
From WireCAD Online Help
Wirecadadmin (Talk | contribs) (Created page with " == DRAFT == The following outlines the use of MS SQL Azure database service with WireCAD v8. == What You Should Know == #This is an outline only. Not a full tutorial. #Yo...") |
Wirecadadmin (Talk | contribs) |
||
| Line 10: | Line 10: | ||
#You can avoid the setup frustration of SQL Azure by purchasing the service from us. | #You can avoid the setup frustration of SQL Azure by purchasing the service from us. | ||
#WireCAD v8 on SQL Azure is structured to use a single database. This differs from the standard WireCAD approach where each project and the Global Equipment database is a separate database. In SQL Azure we use the database schema names to separate projects and the global database. This allows you to reduce cost since MS Azure is billed by database count and data i/o and storage requirements. | #WireCAD v8 on SQL Azure is structured to use a single database. This differs from the standard WireCAD approach where each project and the Global Equipment database is a separate database. In SQL Azure we use the database schema names to separate projects and the global database. This allows you to reduce cost since MS Azure is billed by database count and data i/o and storage requirements. | ||
| + | #SQL Azure requires you to create Azure firewall rules for each device that will connect to the database server. Don't be alarmed by this as you can install a rule that let's all locations in. | ||
Revision as of 18:19, 20 November 2015
DRAFT
The following outlines the use of MS SQL Azure database service with WireCAD v8.
What You Should Know
- This is an outline only. Not a full tutorial.
- You can avoid the setup frustration of SQL Azure by purchasing the service from us.
- WireCAD v8 on SQL Azure is structured to use a single database. This differs from the standard WireCAD approach where each project and the Global Equipment database is a separate database. In SQL Azure we use the database schema names to separate projects and the global database. This allows you to reduce cost since MS Azure is billed by database count and data i/o and storage requirements.
- SQL Azure requires you to create Azure firewall rules for each device that will connect to the database server. Don't be alarmed by this as you can install a rule that let's all locations in.
