Skip to content

Commit 83301a1

Browse files
committed
Remove runbook task; add profiling PS scripts and docs
Removed redundant CreateOrUpdateRunbookConfigureTask and its project reference. Added profiling PowerShell scripts and documentation to WebJob.Office365ActivityImporter project so it's seen in VS solution tree, including details on SQL script handling and profiling logic in readme.md.
1 parent a191b5d commit 83301a1

File tree

4 files changed

+9
-38
lines changed

4 files changed

+9
-38
lines changed

src/AnalyticsEngine/App.ControlPanel.Engine/App.ControlPanel.Engine.csproj

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,6 @@
7474
<ItemGroup>
7575
<Compile Include="BaseInstallProcessClasses.cs" />
7676
<Compile Include="InstallerLogs.cs" />
77-
<Compile Include="InstallerTasks\JobTasks\CreateOrUpdateRunbookConfigureTask.cs" />
7877
<Compile Include="InstallerTasks\JobTasks\ProfilingScriptsUploadToBlobStorageTask.cs" />
7978
<Compile Include="InstallerTasks\JobTasks\AutomationAccountTask.cs" />
8079
<Compile Include="ConfigureAzureComponentsTasks.cs" />

src/AnalyticsEngine/App.ControlPanel.Engine/InstallerTasks/JobTasks/CreateOrUpdateRunbookConfigureTask.cs

Lines changed: 0 additions & 37 deletions
This file was deleted.

src/AnalyticsEngine/App.ControlPanel.Engine/SqlExtentions/readme.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,3 +10,8 @@ The scripts are run after the database schema has been updated with Entity Frame
1010

1111
Note: SQL server doesn't normally support "```GO```" statements in stored procedures ("GO" is a SQL Server Management Studio thing to separate scripts in a single file), so you should avoid using them in your scripts here.
1212
You *can* use the "GO" statement and the installer will split each segment by "GO" and then execute each segment (bit of a hack), but you should put the scripts in separate files or remove "GO" from any script here.
13+
14+
## Profiling Extensions
15+
These scripts setup the SQL Server profiling extensions but are run by PS scripts found in /src/AnalyticsEngine/WebJob.Office365ActivityImporter/AutomationPS/ProfilingJobs/.
16+
17+
The main logic is in "usp_CompileWeekly" - a stored procedure that compiles weekly profiling data from daily profiling data.

src/AnalyticsEngine/WebJob.Office365ActivityImporter/WebJob.Office365ActivityImporter.csproj

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -115,6 +115,10 @@
115115
<None Include="App.Release.config">
116116
<DependentUpon>App.Template.config</DependentUpon>
117117
</None>
118+
<None Include="AutomationPS\ProfilingJobs\Aggregation_Status.ps1" />
119+
<None Include="AutomationPS\ProfilingJobs\Database_Maintenance.ps1" />
120+
<None Include="AutomationPS\ProfilingJobs\Weekly.ps1" />
121+
<None Include="AutomationPS\readme.md" />
118122
</ItemGroup>
119123
<ItemGroup>
120124
<ProjectReference Include="..\Common\DataUtils\DataUtils.csproj">

0 commit comments

Comments
 (0)