I previously wrote a blog post called Index data without writing code and recently received some interesting comments / questions in regards to using the Collection(Edm.String) collection datatype when having a SQL Server based data source. And I therefore decided to compile the information within a separate blog post. (Special thanks to the Azure search team for answering some of my queries!)
Within part 2 of this series (click here for part 1), I would like to cover some of the available configuration options of the Azure API SQL Server connector. The connector simply enables you to connect with a SQL Server (as well as on-premises instances) or Azure SQL Database and perform various actions. This includes; executing stored Procedures, Poll data (triggers) and the option to retrieve, create, update and delete database table entries without having to write SQL.
Within this series (well just two posts) I want to cover some of the available configuration options of the Azure API SQL Server connector. The connector simply enables you to connect with a SQL Server (as well as on-premises instances) or Azure SQL Database and perform various actions. This includes; executing stored Procedures, Poll data (triggers) and the option to retrieve, create, update and delete database table entries without having to write SQL.
I like to keep a close eye on my servers and users/customers. However, not want to do everything manually. This is not only very time consuming, but also most likely to find important issues rather late, hence the script below.
The SQL Server SMO client API can be used query and alter settings and objects within your SQL Server instances. In case you want to query your user database; you will run into some limitations. The client API isn’t aware of your data objects and, therefore, not exposing a typed scheme. Fortunately, it’s pretty easy to accomplish when using the SQL Server PowerShell Module (SQLPS)
Recent Comments