Comments
Sort by recent activity
I realize this is an older post/announcement, but I just wanted to make sure anyone who does an "uninstall" reads the full "uninstall" document first. / comments
I realize this is an older post/announcement, but I just wanted to make sure anyone who does an "uninstall" reads the full "uninstall" document first.
Not sure how this was even possible with the "Support and Upgrade" expired, but the backup instance in Production had the "GUI" components set to 10.1.18.2060 but the "server components" were still 10.0.14.1166. Update was done in June. Removed the GUI component, re-installed the 10.0.14.1166 version and backups appear to be working correctly. Manually ran a "RESTORE VERIFYONLY" on a few files to confirm they were OK. [image] [image] / comments
Not sure how this was even possible with the "Support and Upgrade" expired, but the backup instance in Production had the "GUI" components set to 10.1.18.2060 but the "server components" were still...
Glad I found this! I just lost a lot of work (code) that I had not saved (**SIGH**... save and save often) and thought it was related to SSMS 18.9.1! Right clicking on a tab caused the entire session to just disappear. Release 10.6.14 appears to have solved this issue. / comments
Glad I found this! I just lost a lot of work (code) that I had not saved (**SIGH**... save and save often) and thought it was related to SSMS 18.9.1! Right clicking on a tab caused the entire sessi...
Note sure if this is related, but after a Windows 10 update (KB4528760), when in SSMS (17.9.1/14.0.17289.0), checking for an update of SQL Prompt (10.0.1.12389) throws an error, then SSMS restarts. Downloading the SQLPrompt installer and manually updating SQL Prompt to 10.0.8.13382 appeared to have resolved the problem. / comments
Note sure if this is related, but after a Windows 10 update (KB4528760), when in SSMS (17.9.1/14.0.17289.0), checking for an update of SQL Prompt (10.0.1.12389) throws an error, then SSMS restarts....
I tried to re-submit a ticket for this, as the problem has not been resolve and this is now causing serious issues, since we are unable to schedule or perform additional backups/restores. / comments
I tried to re-submit a ticket for this, as the problem has not been resolve and this is now causing serious issues, since we are unable to schedule or perform additional backups/restores.
Thanks for the update. I was waiting for a few days for some of the backups to complete, as one of the DBAs accidently changed the full backup jobs from 8 threads to 32 threads.
After the backups completed last week (and nothing else was running from a backup standpoint), we are still getting the "Execution Timeout Expired" when trying to use the SQL Backup GUI (just trying to start the GUI up and review jobs, etc.). I tried again today (with a full backup running, 8 threads this time).
Regarding the log backups, we backup directly to the NAS (another server on the network with Dell Compellent attached). We are not using the "COPYTO" option.
/ comments
Thanks for the update. I was waiting for a few days for some of the backups to complete, as one of the DBAs accidently changed the full backup jobs from 8 threads to 32 threads.
After the backups ...
FYI, I also ran this: EXECUTE master..sqbmemory Results:
Type Minimum Maximum Average Blk count Total
Commit 4096 33865138176 234573 4871073 1142622560256
Reserve 4096 1203238535168 509933 4848140 2472231276544
Free 4096 134915153526784 188614352755 727 137122634452992
Private 4096 1203238535168 371940 9717951 3614502526976
Mapped 4096 67108864 295756 320 94642176
Image 4096 29757440 272470 942 256667648
/ comments
FYI, I also ran this: EXECUTE master..sqbmemoryResults:
Type Minimum Maximum Average Blk count Total
Commit 4096 33865138176 234573 4871073 ...
FYI, I did open a ticket with Support (it was getting EXTREMELY frustrating having my system lock up every 15-20 minutes)... installed SQL Prompt 9.1.5 and the issues appear to have been resolved! Thanks! [image] / comments
FYI, I did open a ticket with Support (it was getting EXTREMELY frustrating having my system lock up every 15-20 minutes)... installed SQL Prompt 9.1.5 and the issues appear to have been resolved! ...
While SQL Prompt may have issues related to having "Enable Code Analysis" option enabled, I am beginning to think SSMS 17.5 might be causing the issue? I stopped the RedGate client service and disabled all of the SQL Prompt and still see periodic system freezing, with high WmiPrvSE CPU usage. I do know the problem goes away when all of the SSMS sessions are stopped. / comments
While SQL Prompt may have issues related to having "Enable Code Analysis" option enabled, I am beginning to think SSMS 17.5 might be causing the issue? I stopped the RedGate client service and dis...
There is another thread that discusses the same problem with slowness and freezing... Here are some additional findings so far: 1. After disabling the "Enable Code Analysis" option, the freezing went away as I mentioned before. 2. Something (either SSMS or RedGate Prompt) is causing periodic slowness on my PC where either SSMS would have a hour glass (spinning circle) or my entire system would suddenly stop responding. - Note that,with stopping all instances of SSMS (I typically an have 4-6 running at once), the problem went away. 3. The problem appears to be related to WmiPrvSE.exe / comments
There is another thread that discusses the same problem with slowness and freezing... Here are some additional findings so far: 1. After disabling the "Enable Code Analysis" option, the freezing we...