Viewing 15 posts - 1,501 through 1,515 (of 2,919 total)
I imagine this depends on your CMS.
But it sounds like a use case for SSIS to me. With SSIS you can have it fire queries against multiple databases simultaneously 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.
My opinion - you get what you pay for.
The authors of the books need to make money, so they write books on what they know.
If free training is what you...
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.
Found this article:
https://dba.stackexchange.com/questions/114572/why-does-updlock-cause-selects-to-hang-lock
From that link, the solution is to have a better index. Now, that being said, I would expect that since you are doing a SEEK, your index is...
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.
Sounds to me like windows permissions are set wrong. You said you can't access it from Windows run menu OR from SQL Server, this makes sense. If you have no...
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.
Have you tried using CAST or CONVERT to pick a data type on the column that has an unknown datatype? Not the best solution, but will solve the problem.
What I...
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.
Gotta love it when SQL can't guess how long the rollback will take so it tells you 0% and 0 seconds. I've seen that before and there is that panic...
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.
Sorry I couldn't be more help, but I am stumped on this one.
I am confident that restarting the SQL Server service will fix the issue, but I am confused why...
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.
Well, I'm confused... the query I gave should have shown you the rollback status on the query. Since sysprocesses and sp_who2 are both saying it is rolling back, my next...
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.
Since the query didn't return anything, my thought is the rollback completed successfully. Where are you seeing the "killed/rollback" information?
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.
I am pretty sure that if the SSIS service is not running, you can't do most SSIS related tasks such as deploying to an SSIS catalog.
I am a little surprised...
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.
Viewing 15 posts - 1,501 through 1,515 (of 2,919 total)