Viewing 15 posts - 18,826 through 18,840 (of 59,072 total)
titsiros (12/23/2015)
Yes
It's going to a bugger then. One of the two client's IDs are all going to have to change and you'll need to ensure that reference tables are...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2015 at 6:11 pm
Wouldn't a CASE statement do the trick here?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2015 at 6:05 pm
SQLisAwE5OmE (12/24/2015)
Yes, it's giving me all activities between 11/30 to 12/1.Correct?
Technically, not correct especially since "BETWEEN" in T-SQL is inclusive of both end values.
Scott's code giving you all activities...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2015 at 4:40 pm
RonKyle (12/24/2015)
That's a pretty jerk answer.
Sorry, but I don't agree. Maybe it could have been phrased differently, although I don't see anything wrong with it. But the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2015 at 4:27 pm
Jason A. Long (12/24/2015)
How about this one?
Now you're cooking with gas. MUCH better data and test!... and, I stand corrected.
1. If all you want to do is display...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2015 at 4:24 pm
johnwalker10 (12/23/2015)
try the below query to get result in DD/MM/YY format.
select LEFT(convert(varchar(10), @date, 103),6) + Right(Year(@date)+ 1,2)
Gosh, no... Never do date/time formatting for a GUI from SQL Server. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2015 at 3:16 pm
Ok... if have to ask... why was the following post marked as the correct answer...
johnwalker10 (12/23/2015)
ALTER TABLE [dbo].[ table_name] DROP CONSTRAINT [fk_name]
... even though it has less information that this...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2015 at 3:13 pm
You've confused me a bit, Scott. First you say that 16 VLFs for a 1GB logfile is too low and then you explain using even fewer VLFs per GB...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2015 at 3:09 pm
Basurmanin (12/24/2015)
i have the next problem:
i need to extract numbers from a string.
Without using CTE, func, proc. Just query.
Restrictions - varchar (50)
Let`s take this example
select 'aGk5kyO8pfas2csd444567' as word union...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2015 at 2:56 pm
SQLisAwE5OmE (12/24/2015)
Thanks Scott, it worked.Appreciate it.
Do you understand the code that Scott wrote and why it's better to use the >=/< method he used?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2015 at 2:37 pm
It's not just the anchor. You can't use a Non-Clustered Index for the QU because of the possibility of a "Merry-go-Round" index.
Also, your data is sorted on the Amt...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2015 at 2:13 pm
Jeff Moden (12/23/2015)
mpdillon (12/23/2015)
Yes. I agree that would work. I was hoping to find a query solution. I was thinking that if the table were Ordered by item number...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2015 at 2:05 pm
david.holley (12/23/2015)
I'm incredibly bad at math and doing conversions, but I make a killer Pineapple/Jalapeno caserole.
Heh... sounds awesome! 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2015 at 9:50 am
mpdillon (12/23/2015)
Yes. I agree that would work. I was hoping to find a query solution. I was thinking that if the table were Ordered by item number and Start...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 23, 2015 at 7:04 pm
Do the tables use IDENTITY columns for the PK of the tables?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 23, 2015 at 6:45 pm
Viewing 15 posts - 18,826 through 18,840 (of 59,072 total)