Viewing 15 posts - 9,151 through 9,165 (of 59,102 total)
If you're not using at least SQL Server 2012, the feature/syntax doesn't exist prior to that. You say you're using v17 but what is that for? SSMS? That's not what...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 18, 2019 at 4:15 am
Mya be you have some different collation or timezone setting. Here is what I am getting. 6/14/2019 5:00:00 PM
My recommendation would be to rewrite it so that it does...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2019 at 4:16 pm
So I come across this thread nine years and several iterations of SSMS after the event, totally fed up with having to restart SSMS repeatedly, often losing work along...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2019 at 2:10 pm
Perhaps for the same reason jackrabbits run in front of cars?
Heh... and squirrels. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2019 at 1:37 pm
To answer the logically next expected question...
https://www.google.com/search?&q=save+powershell+output+to+table+in+sql+server
Of course, I don't have a code example for this because I don't use PowerShell to do such things, especially since the list...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2019 at 1:12 pm
Heh... perhaps the next article should be about the delays of ghost row cleanups. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2019 at 12:31 pm
I'll never understand why some people write 100's of lines of code without testing the code before turning it into a stored procedure or whatever and wether or not there...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2019 at 12:14 pm
I'm going to suggest that you DON'T make such an over-arching delete system. There may be a need for different instances/systems to do the deletes of old backup files on...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2019 at 12:17 am
p.s. Since the forum software still provides no easy method back to the article being discussed, here's the link to the original script article, if anyone is interested.
https://www.sqlservercentral.com/scripts/add-working-days-but-avoid-holidays-2
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2019 at 12:11 am
Thought I'd throw my 2 cents in from a presentation I did nearly a decade ago and it still works to allow the secure operation of xp_CmdShell. Here's the full...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2019 at 11:40 pm
It also depends on what the package is doing...and whether or not I have to connect to SQL Server for other configuration values.
That same thought is usually the justification...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2019 at 3:08 pm
I would like to know if corruption/unavaialability of one partition would impact whole DB? Will I still be able to access rest of the partitions? Can I take one...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2019 at 12:01 am
Hmmph... additionally, the "Free" online version is limited to 100 lines of code. The non-free versions aren't expensive but, considering the bug I found above, I wouldn't spend a nickle...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2019 at 11:51 pm
A lot of people make the mistake of thinking that a CTE is rendered as a separate object. Unless there is a "blocking operator" in the CTE, it's treated like...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2019 at 11:48 pm
Thanks for taking the time, Henrik. A lot of people will continue to be "stuck" in 2008 R2 for one reason or another and so I wanted to know what's...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2019 at 11:34 pm
Viewing 15 posts - 9,151 through 9,165 (of 59,102 total)