Viewing 15 posts - 1,561 through 1,575 (of 2,917 total)
You can read it from another location, but you may be missing the symbol libraries. If possible, it is best to do it on the server that had the problem...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 16, 2020 at 5:32 pm
As a thought, it may not hurt to reach out to the creators of "Relativity" to see what they recommend. Often the creators of the tool will have some good...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 16, 2020 at 4:54 pm
That is a fun one with NULLs. The problem is that @x=@tempX can be true or false when either of those is NULL. Doing a comparison on if @x=NULL or...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 16, 2020 at 4:40 pm
Pretty sure SQL has no built in way to monitor and alert for stack dumps.
This link has a powershell script for it though:
https://www.sqltechnet.com/2014/04/monitor-and-alert-sql-stack-dumps.html
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 16, 2020 at 4:27 pm
UPDATE needs to look through the table to find the row(s) that needs updating. INSERT can just put a new row in the proper place (heap or index) without needing...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 16, 2020 at 3:49 pm
I would monitor the logs in that case. Or long running queries. If most queries complete in under 5 seconds, but I start seeing a large number of transactions being...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 16, 2020 at 3:30 pm
generally, when a stack dump happens, the process that caused the stack dump shuts down. In this case, SQL Server service is likely no longer running after the stack dump...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 16, 2020 at 3:05 pm
My approach - dig into the facts before digging into possible symptoms. Spikes in CPU don't mean there is a SQL issue. Monitoring for spikes MAY help or may not...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 16, 2020 at 2:46 pm
I'd check in your logs to see what happened. both windows and SQL Server logs.
A good write up on latch timeout can be found here:
https://mssqlwiki.com/2012/09/07/latch-timeout-and-sql-server-latch/
It includes some steps to troubleshoot...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 15, 2020 at 9:42 pm
There is a lot in this question.
First, a "heap" with a "clustered index" is no longer a heap. A heap is an unordered set of data. A clustered index orders...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 15, 2020 at 2:43 pm
Another thing to add in to what Jeff said is if you are a contractor working on this, make sure to include your support costs for if/when the application fails. ...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 14, 2020 at 4:45 pm
I started with CVS then SVN and finally to Git (via GitLab). My opinion though, terminology needs to be standardized. GitHub has "Pull Request" to get the source branch pulled...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 14, 2020 at 4:31 pm
I actually really liked the uCertify course for MTA-Database Fundamentals. That is the one I took for getting my MTA. That being said, if you have used SQL Server for...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 14, 2020 at 2:53 pm
Possibly a dumb question, but are both DEV and PROD using the same account to run the tool that connects to SQLPROD? I mean an AD account, not a "local...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 11, 2020 at 8:09 pm
if the ID field was an IDENTITY, you generally don't include it in your INSERT statements as SQL will auto-increment it. If you include a value, you need to SET...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 11, 2020 at 7:59 pm
Viewing 15 posts - 1,561 through 1,575 (of 2,917 total)