Viewing 15 posts - 31,051 through 31,065 (of 59,101 total)
Gosh, Eli. Thanks for sharing but please consider the following, instead. It's faster, still doesn't require access to a table, can produce a much larger range of numbers,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2012 at 12:01 pm
opc.three (2/18/2012)
Jeff Moden (2/18/2012)
opc.three (2/18/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2012 at 11:21 am
walia_jagwinder (2/19/2012)
Clustering allowing one physical server to take over tasks and responsibilities of another physical server that is failed.Does clustering also increasing the data access performances?
If yes then how?
As Gail...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2012 at 10:59 am
SQL Kiwi (2/16/2012)
Stewart "Arturius" Campbell (2/16/2012)
will this help?
This is an unreliable and unsupported construct, and should not be used or recommended:
CREATE TABLE #test (col1 tinyint, col2 char(5));
INSERT #test (col1)
VALUES...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2012 at 10:50 am
It would be extremely beneficial to your cause if you posted the data in a more readily consumable format than an Excel spreadsheet. Please see the first link in...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2012 at 10:43 am
Heh. Not to worry. I've eaten my own share of bad beans. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2012 at 7:03 pm
ColdCoffee (2/18/2012)
DECLARE @Table TABLE
( ColVal VARCHAR(10) )
INSERT INTO...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2012 at 6:35 pm
ColdCoffee (2/18/2012)
Jeff Moden (2/18/2012)
Although the execution plans are identical and the performance is likely identical, as well, sometimes the "old ways" lead to simpler code. Don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2012 at 6:31 pm
opc.three (2/18/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2012 at 6:29 pm
rfr.ferrari (2/18/2012)
nice article Jeff!thanks!!!!
You bet. Thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2012 at 11:57 am
I've not checked any of the other's code (not real good at reading PowerShell code) but make sure they can handle multiple days.
Just because it's my nature, I thought I'd...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2012 at 11:44 am
ColdCoffee (2/18/2012)
DECLARE @Table TABLE
( ColVal VARCHAR(10) )
INSERT INTO @Table (ColVal)
SELECT 'name1'
UNION ALL SELECT 'name2'
UNION ALL SELECT 'name3'
UNION ALL SELECT 'name1'
UNION...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2012 at 10:33 am
I don't believe that the VARCHAR(MAX) datatype is the problem. I believe it's just the shear amount of data you're trying to transfer through the pipe. You said...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2012 at 10:19 am
GuruGPrasad (2/16/2012)
Hi Jeff Moden,Yes my post was blocked.. Its ok no problem
Regards
Guru
It was problem enough for you to mention it. 😀 I looked back at your posts on...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2012 at 10:10 am
SQLKnowItAll (2/16/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2012 at 10:07 am
Viewing 15 posts - 31,051 through 31,065 (of 59,101 total)