Viewing 15 posts - 21,256 through 21,270 (of 59,072 total)
What's in this table? Is it by any chance something like a log, audit, or invoice detail table?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 8:17 pm
ricardo_chicas (3/14/2015)
I have a box with SQL Server 2008 R2, at the latest SP and CU, 16 cores and 196gb of ram (I also tested it at a copy...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 7:13 pm
Thanks, Terry. Sounds like you've done it right on the archive side.
On the DELETEs, remember that they affect ALL indexes and ALL FKs pointing at the table. If...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 6:55 pm
Just for grins, here are the results from the same test harness with only 500,000 rows. The times here will likely be shorter than for your production run because...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 6:47 pm
Awesome. I love helping but when someone that we've helped get's a great wow-factor on top of it all, that makes my day, as well. Thanks again for...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 6:43 pm
thomashohner (3/14/2015)
I ran both convert codes and on my limited test data (1,000 rows) they were both uber fast. Not even a 1...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 6:19 pm
Eirikur Eiriksson (3/14/2015)
With the integer you will have to reverse the byte order, here is a quick example😎
DECLARE @COLOURINT INT = 14745599;SELECT CHAR(35) + CONVERT(VARCHAR(6),SUBSTRING(CONVERT(BINARY(3),@COLOURINT,1),3,1) + SUBSTRING(CONVERT(BINARY(3),@COLOURINT,1),2,1) + SUBSTRING(CONVERT(BINARY(3),@COLOURINT,1),1,1),2)
Result
#FFFFE0
I make...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 4:44 pm
thomashohner (3/14/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 4:31 pm
Huh... It's been a long time since I've played with hex in SQL Server. I believe I may have an even better and faster way than what I posted....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 2:00 pm
This will really make it so you don't want to use the scalar function you posted. The sys.fn_varbintohexstr function calls yet another scalar function called sys.fn_varbintohexsubstring and it not...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 12:58 pm
thomashohner (3/14/2015)
Yes sir,Did I say it wrong on what data type it should be?
Oh no... You did fine. It's just that I can't even spell "SSRS" and, although...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 12:44 pm
thomashohner (3/14/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 12:08 pm
Ed Wagner (3/13/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 11:57 am
SQLAssAS (3/12/2015)
In SQL 2005 if i was trying to insert some data with a text qualifier inside a text qualified field, it would work, for example:
"Name","ID ","Location","","Comany",""House Name" Road",
In SQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 11:54 am
nickwelhar (3/14/2015)
More XML Parser examples...Nick
Thanks for that (and I'm serious. Thank you very much!). I'm not a C# programmer but, as a DBA, I've always wanted to know...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 11:43 am
Viewing 15 posts - 21,256 through 21,270 (of 59,072 total)