I have SQL Server job. In the last step of the job, I want to stop/start SQL Server.
Next, I created
.bat file with
NET STOP "MsSqlServer"
I tried SSIS package that uses the execute process task with
cmd.exe and then execute the
.bat file to restart
mssqlserver and it works fine...
However, when I called this package in the SQL Server job, it stops the service but does not not start it back.
the question is how to stop/start sql server after another sql serve job complete..?
i have sql server/analysis services/reporting services in one station with 64 GB Memory.and i have nightly job with this steps :
- 1-ETL that Update DW
- 2- Process Analysis services Database
- 3-Update Reporting services Subsciptions
Sometimes, in beginning the AS Processsing in the step 2, it gives me
error: there is no resource Available and and the job got failed.
All I want is a good memory configuration for this environment.
what strategy I must choose for Memory Management ?
Another problem: After step 2 for update subscription (i have about 50 Subscriptions), if I try
Update Subscription with clean memory (after I restart SQL Server service), the subscription executes very fast.
If i don't restart the SQL Services, it take long time to run and sometimes it never gives me results.