« first day (1788 days earlier)      last day (3065 days later) » 

1:59 AM
@dezso Oops! Late night. Touch screen. Sorry! Maybe I should just have called him Eric?
@JackDouglas Which is why I wrote the message, trying to explain my motivation.
@JackDouglas Part of my "reject" vote: I'd didn't want x.10^n review tasks to suddenly materialise. Then again .. review badges .. tasty, shiny badges ... hmmmmm, badges
 
 
6 hours later…
7:53 AM
@MichaelGreen yes that would be a pain
 
 
1 hour later…
9:03 AM
@MichaelGreen that's a good idea
@ypercube isn't it suspicious that recursion is so easy?
 
9:28 AM
@dezso yeah. ridiculously easy ;)
 
@ypercube I can hear the noise of systems crashing because of relying on this 'solution'
 
it's something to wonder how 1 or 2 people commented "yes, this is awesome and works" and upvoted and the crowd just followed.
The answer had +55-1 when I saw it.
 
 
4 hours later…
1:17 PM
licence issues?
user image
2
theoretically from Thailand
 
 
1 hour later…
2:27 PM
Rightclick as in bring up the menu showing properties. — Dave Ward 34 mins ago
could not imagine what a right click was, now I'm enlightened
 
@dezso Actually being used to ssis/visual studio that answer makes perfect sense
 
@dezso A "solution" may be a type of object in VS, kind of like a project group, I think. When I close SSMS with several unsaved query windows, it asks me whether I want to save my stuff, showing a mini-tree the root item of which is typically "Solution1" followed by leaves like "SQLQuery1", "SQLQuery2" etc.
 
not that it will solve the problem, i think
 
I couldn't understand that answer either
The wording seems recursive:
> The correct **solution** to this is to:

right click on the **solution**
 
Yes, the two meanings definitely clash there, no wonder people are confused.
 
2:45 PM
@TomV that explains a lot
 
3:00 PM
@dezso "solution" is just a level above "projects" in the "solution explorer" pane
 
3:10 PM
@TomV I've added a comment there, please improve on it, if needed
 
3:21 PM
@dezso I think that should be clearer now
I edited your comment to make it a bit more clear, but I don't see how that property would have an impact on the generation of packages from BIML. It would be nice if you could add some information on 'how' your solution would work for the OP — Tom V 8 secs ago
 
@TomV great, I've removed my comments
 
 
2 hours later…
5:11 PM
does anyone see any reason to not use xp_fixeddrives to determine what drive letters are available to SQL Server 2005+ ? I don't see it as deprecated; however since it is an undocumented feature, that doesn't surprise me.
 
5:31 PM
@MaxVernon not much, no, except it doesn't show you the original space, only the free one
 
@Marian thanks. I'm only interested in the drive letters SQL Server uses for databases\logs
 
@MaxVernon you'll have to filter that, unfortunately
 
@Marian I'm actually trying to ensure a certain database has been dropped, and it's files removed, in an automated fashion, using xp_cmdshell, so knowing all the drive letters SQL Server can "see" gets me most of the way there! Thanks for your help!
I'm also going to get some path info from the msdb backup-related tables.
 
5:54 PM
@MaxVernon I tend to just use sys.master_files something like DISTINCT LEFT(physical_name,1). Just because you can more easily do something with that data, versus the XP you have to dump to table and all that.
 
 
1 hour later…
7:03 PM
@ShawnMelton lol, I'm using a cursor to run xp_cmdshell on each drive letter multiple times looking for a known path using DIR /b /s kind of thing, so in this case I actually need the temporary table anyway. I should probably be doing this in PoSH.
 
@MaxVernon that's bèèèèd
 
@TomV looool
 
@MaxVernon Or just call Posh in your xp_cmdshell, would likely be more efficient that the dos prompt DIR.
 
@ShawnMelton maybe.... although xp_cmdshell loads cmd.exe which contains the dir function natively anyway, so maybe not.
 
PowerShell contains dir natively as well
 
7:06 PM
xp_cmdshell would still have to load cmd.exe, and then load ps.exe
 
You might also do this quicker in SQL CLR...if you wanted to dig that whole.
 
That's a pretty big hole for what I need to do.
 
:)
I used xp_cmdshell and PowerShell to build out storage monitoring and reporting for customer few years ago. It worked out pretty well, not sure using Posh to search directories would compare to just native command with DOS.
 
I bet you have a lot more functionality in the PoSH version, which might be nice depending on requirements.
 
@MaxVernon I was holding on to old habits but have entirely switched to powershell and I'm so loving it
I come from a *nix background and found cmd.exe extremely lacking, but POSH is killing bash and off course cmd
 
7:12 PM
@TomV I've gotta spend the time to do that. I was just hoping I could do a dir C:\some\*\path\* but of course that don't work in Windoze.
gotta love ls for that.
 
I was typing, "ls would do that without worries" :)
 
@TomV not that my *nix skillz are that great, but I regularly use AIX here so I'm getting better at it.
on another note entirely, Windows 10 Mobile on my Lumia 950 XL is a bit on the "beta" end of things. Plus, no "Here Drive+", which really bites. On a positive side, Microsoft is shipping me a free Display Dock which should be here next week so I can try out Continuum.
 
7:30 PM
I must say wireless charging is great! Not having to plug in the phone is far sweeeeter than I imagined it would be.
 
I have a lumia, best thing is, dynamics AX 7 is cloud based, works on every phone except WP
 
@TomV I wonder if it works with the Edge browser on Windows 10 mobile?
 
@MaxVernon 11(+) so probably
 
 
2 hours later…
9:50 PM
@Lamak Hope you're safe.
 

« first day (1788 days earlier)      last day (3065 days later) »