Viewing 15 posts - 31,651 through 31,665 (of 59,099 total)
Alright, Bill... here we go!
First, we need a little bit more data than what you provided so we can see this work. A million rows spread out from 2000-01-01...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 16, 2011 at 10:00 pm
SQLKnowItAll (12/15/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 16, 2011 at 6:16 am
MysteryJimbo (12/16/2011)
Completely off the walll and not what I would do, but you could start SQL Agent job with powershell steps from a stored procedure.
I don't believe that's such an...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 16, 2011 at 6:02 am
bill.sutcliffe (12/15/2011)
I've read part 1 and 2 of your articles and also the article on the Tally table. It looks like you hard code the months in your SUM...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2011 at 8:24 pm
bill.sutcliffe (12/15/2011)
I've read part 1 and 2 of your articles and also the article on the Tally table. It looks like you hard code the months in your SUM...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2011 at 8:22 pm
Fraggle-805517 (12/15/2011)
An update on this. The MAXDOP statement worked the best. It took the entire process down from 8-15hours to under 5 minutes.Thanks,
Nathan
Heh... call it what...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2011 at 7:46 pm
SQLRNNR (12/15/2011)
Create a proxy and execute the job with the proxy account.
Basically, yes. You just need to do it in a way where the low-priv user doesn't even need...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2011 at 7:36 pm
SQLKnowItAll (12/15/2011)
Does that not defeat the point?
Not in my book. 🙂 Think about why they added the CLR capability... it's to extend what you can do from a...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2011 at 7:29 pm
That's why I asked the question. The ROW_NUMBER() thing is necessary if the OP wants separate columns and isn't necessary if a space delimited, multi-element column is all that's...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2011 at 7:19 pm
Post withdrawn... didn't read the requirements quite right.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2011 at 4:59 pm
There are ways to allow for the system to execute xp_CmdShell and for users to execute stored procedures that contain xp_CmdShell without the users being able to execute xp_CmdShell and...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2011 at 4:56 pm
newbieuser (12/15/2011)
I would...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2011 at 4:53 pm
Brandie Tarvin (12/15/2011)
Why would you put your CLUSTERED index on the ID field of the table?
To prevent page splits on a massive table.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2011 at 4:48 pm
SQLKnowItAll (12/15/2011)
One of the questions that my co-worker had was how we call or open a session of PowerShell in a stored proc. I believe the answer is "you don't."
BWAA-HAAA!!!!...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2011 at 4:43 pm
Do you want separate columns or do you want a single column with items separated by spaces?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2011 at 4:34 pm
Viewing 15 posts - 31,651 through 31,665 (of 59,099 total)