Viewing 15 posts - 32,326 through 32,340 (of 59,102 total)
Something else you need to be aware of that some of us found out while testing code in one of my articles... certain collations will make your server run horribly...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 6:03 pm
opc.three (10/7/2011)
Please, have a look at PowerShell. Once you ramp up you will never want to open CmdShell again.
Well I might especially if it's to fire off PowerShell from a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 5:47 pm
For those interested in what some of the more cryptic designations for ASCII characters less than character 32 are, please see the following link...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 4:39 pm
No... T-SQL isn't a good parsing tool for such a thing. What are you trying to parse out of the Text documents and what's the average length of these...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 4:34 pm
Performace Guard (Shehap) (10/9/2011)
update TableA SET COL4=COL2 from ( select col2,col3 from TableB )AS s INNER JOIN TableA...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 4:32 pm
ALZDBA (10/9/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 2:06 pm
Hmmm... Learning Service Broker would mean that I'd have to learn another SQL Server "4 letter word" 😛 but it does sound interesting. What I'd be most interested in...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 12:13 pm
yubo1 (10/9/2011)
HI Jeff.Thanks a lot
You bet... thank you for taking it the right way.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 12:06 pm
Performace Guard (Shehap) (10/9/2011)
alter function dbo.Returnvalues (@string VARCHAR (50))
returns @TEMPTBALE table(newstring varchar (50))
as
begin
declare @value...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 12:00 pm
Jags2001 (10/9/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 11:48 am
David Moutray (10/9/2011)
Jeff Moden (10/9/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 11:43 am
David Moutray (10/9/2011)
I played around with it for a bit, and got it to work, though. Paste the XML into Notepad...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 11:38 am
Perhaps it's because I'm using SQL Server 2005 on a 9 year old, single CPU box, but I've tried the index suggestions from dmoutray's testing above, especially the 0 second...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 7:57 am
dmoutray (10/8/2011)
Just copy and paste the XML into SQL Server Management Studio to see the graphical execution plan.
That's just not working for me... is it because I'm using SQL Server...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 7:44 am
Interesting stuff (hang on a minute... gotta get this shoe out of my mouth... 🙂 there, that's better)... I wouldn't have believed that this query could ever be helped by...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 7:30 am
Viewing 15 posts - 32,326 through 32,340 (of 59,102 total)