Comments
Sort by recent activity
Alex B said:
Hi all,
After working with @easby in a ticket, the issue is that an old view from v10 remained in the repository that had the same name as a new table being introduced. Running this before updating (or on the repository database after updating and getting the error above) should allow the schema upgrade to continue:
DROP VIEW [settings].[MonitoredEntities]
Kind regards, Alex
Will a revised setup installer be released to check (and potentially solve) this issue during installation? / comments
Alex B said:
Hi all,
After working with @easby in a ticket, the issue is that an old view from v10 remained in the repository that had the same name as a new table being introduced. Running...
Could you perhaps shed some more insight into your environment? What build version does your SQL server and SQL Monitor have? What kind of HW are you hosting the database on? / comments
Could you perhaps shed some more insight into your environment?What build version does your SQL server and SQL Monitor have?What kind of HW are you hosting the database on?
TeunvdBiggelaar said:
I still receive these kinds of errors when im trying to open alerts and i'm on version 13.0.51.53 in our development environment.
I'm guessing your issue is another one than the one Don was facing. He had issues when people were logging in. When viewing an alert you're already logged in? Or are you opening links from emails? Perhaps provide some more details and perhaps open another topic if the issue you're facing is not exactly the same. / comments
TeunvdBiggelaar said:
I still receive these kinds of errors when im trying to open alerts and i'm on version 13.0.51.53 in our development environment.
I'm guessing your issue is another one...
Hi @DonFerguson, We're on 13.0.48 and I just checked with some of our non-admin users and nobody is having issues to log in. / comments
Hi @DonFerguson, We're on 13.0.48 and I just checked with some of our non-admin users and nobody is having issues to log in.
You have to use 'ALTER INDEX' instead of 'INDEX'. Mine is configured like: [image] [image] / comments
You have to use 'ALTER INDEX' instead of 'INDEX'. Mine is configured like:
Here we are again ... Where is DBServer2 located? If it is not in de the same region you need to use async commit. Otherwise delay will cause application issues. I recommend you read through this article: https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-overview?view=azuresql The biggest difference with on-prem is: - Load balancer that is needed in Azure - All nodes inside your cluster need to be a member of an availability set - I also recommend using striped volumes for your SQL files to foresee better performance: https://learn.microsoft.com/en-us/gaming/azure/game-dev-virtual-machine/striped-disks-iops Feel free to contact me afterwards if you still have questions. I've done it in the past on SQL 2016 and by the looks of it , not too much has changed. / comments
Here we are again ...Where is DBServer2 located? If it is not in de the same region you need to use async commit. Otherwise delay will cause application issues.I recommend you read through this art...
Using SQL Monitor to capture queries and plans to search for joins could be a start ? You could focus on most resource consuming queries first allowing you to quickly solve the most pressing issues? / comments
Using SQL Monitor to capture queries and plans to search for joins could be a start ? You could focus on most resource consuming queries first allowing you to quickly solve the most pressing issues?
@Alex B, This worked perfect. Thanks a lot for the solution! Kind regards, Thomas / comments
@Alex B, This worked perfect.Thanks a lot for the solution!Kind regards,Thomas
Hi @Victoria W , Logging in as the service account running SQL Monitor is not an option as this will flag a lot of stuff on our security monitoring. / comments
Hi @Victoria W ,Logging in as the service account running SQL Monitor is not an option as this will flag a lot of stuff on our security monitoring.
purplesoup said:
Fabulous! So it looks like if I had 1000 SQL statements I would only have to look at the warnings to filter out the ones that were performing badly?
Are the warnings themselves written to a SQL table so I can query and filter them?
I guess the thing to do is download the trial version and see how I get on...
Be aware that suggested indexes will only improve that specific query. SQL Monitor just uses the information available in the query plan. The index proposal you see will be exactly the same as the one in SSMS. Indexes improving one query could slow down other operations. Be aware on adding indexes without testing thoroughly. Also, depending on the database, not all software vendors support index tuning on their database. Future upgrades or changes could fail if you start fumbling around in the indexes. / comments
purplesoup said:
Fabulous! So it looks like if I had 1000 SQL statements I would only have to look at the warnings to filter out the ones that were performing badly?
Are the warnings themselv...