Azure
/
azure-arch-enterprise-bi-and-reporting
зеркало из https://github.com/Azure/azure-arch-enterprise-bi-and-reporting.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность

Merge pull request #48 from furmangg/patch-1 

fixing spelling
This commit is contained in:
Tyler Clintworth 2017-12-06 13:17:29 -08:00 коммит произвёл GitHub
Родитель c80aba11d9 f51cf225db
Коммит d7be6ae2dc
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
1 изменённых файлов: 3 добавлений и 3 удалений
Показать статистику Скачать Patch файл Скачать Diff файл Показать все файлы Свернуть все файлы

6
User Guides/16-Frequently Asked Questions.md
Просмотреть файл

@ -40,14 +40,14 @@ The TRI does not currently support the swapping of SQL DW with SQL DB.
Although this is not a supported and tested scenario, removal of any node in the architecture should not effect the upstream nodes. As such, you can remove any nodes without seriously effecting the system. This will need to be performed manually in the [Azure portal](https://portal.azure.com) post deployment. Although this is not a supported and tested scenario, removal of any node in the architecture should not effect the upstream nodes. As such, you can remove any nodes without seriously effecting the system. This will need to be performed manually in the [Azure portal](https://portal.azure.com) post deployment.
Keep in mind, the administration UI and other components are not configured to dynamically account for the removal of these nodes so you will still see the presense of these components even though they may not be functional. Keep in mind, the administration UI and other components are not configured to dynamically account for the removal of these nodes so you will still see the presence of these components even though they may not be functional.
### Can I configure the TRI to remove the SSRS scheduled reporting components? ### Can I configure the TRI to remove the SSRS scheduled reporting components?
Although this is not a supported and tested scenario, removal of any node in the architecture should not effect the upstream nodes. As such, you can remove any nodes without seriously effecting the system. This will need to be performed manually in the [Azure portal](https://portal.azure.com) post deployment. Although this is not a supported and tested scenario, removal of any node in the architecture should not effect the upstream nodes. As such, you can remove any nodes without seriously effecting the system. This will need to be performed manually in the [Azure portal](https://portal.azure.com) post deployment.
Keep in mind, the administration UI and other components are not configured to dynamically account for the removal of these nodes so you will still see the presense of these components even though they may not be functional. Keep in mind, the administration UI and other components are not configured to dynamically account for the removal of these nodes so you will still see the presence of these components even though they may not be functional.
### Are the tabular models backed up? ### Are the tabular models backed up?
All tabular model are backed up a storage blob. These can be found under your resource group with the name XXXpntrfsh. All tabular model are backed up a storage blob. These can be found under your resource group with the name XXXpntrfsh.