SQL server down

[Walid Djama]

Hi, 

SQL server agent is crashing few hours after indexation, the consumption of the ram remains very high even after the end of the indexation.

sql server is in a separate server with 16 GB of ram and  the application server is at 32 GB of ram.

Regards

[Nic Brough -Adaptavist- · Accepted solution]

There is something wrong with the settings on your SQL server.  A simple indexing from Jira might cause high load (as it reads every single issue in the database as fast as it can), but it won't crash it.  It's not doing anything other than reading.  If your database can't cope, it's a problem with the database.

[Walid Djama]

So if i understand correctly, if the consumption does not go down after the indexation it's a database problem ? 

[Nic Brough -Adaptavist-]

Possibly.  Have a look at the queries being run - I would expect to see indexing running many sequential reads while running, and then revert to relatively low usage afterwards, writing issue and settings updates as users use Jira and reading when issue views or certain types of query happen (the index and caches are used for most reporting, to keep the level of database access low)