Viewing 15 posts - 1,591 through 1,605 (of 59,067 total)
The 5% / 30% values that where "supposed" best practise are actually a "worst" practise.
BTW and just to be sure... I totally agree with that statement and so do...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2023 at 3:12 pm
Thanks for the reply Grant. I agree using this data must be used with caution. My goal now is to make the stored results more aware of these situations...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2023 at 3:05 pm
Thanks, Steve. Thank you for the feedback.
I'd also considered doing the REVERSE thing and using 4 CHARINDEXes, for such a few elements, it's usually faster than a splitter and re-pivoting,...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2023 at 2:53 pm
Your posted example is great but please Read'n'Heed the article at the first link in my signature line below for future posts for how to post "Readily Consumable" data to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2023 at 12:11 am
Just hire a skilled professionals or a company that can do back office task for you and you can just focus on your core operations.
I've found that to be...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2023 at 7:43 pm
If you're on 2022 then you could use DATE_BUCKET:
WHERE YourDateTimeColumn >= DATE_BUCKET(DAY,1, GETDATE(), CONVERT(datetime,'19000101 16:00:00'))
AND YourDateTimeColumn < DATEADD(DAY, 1, DATE_BUCKET(DAY,1, GETDATE(), CONVERT(datetime,'19000101 16:00:00')))
Another method...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2023 at 7:36 pm
When doing (upsizing wizard), problems appeared in copy (sql server), so I deleted it and installed it again, and after I tried (import), it worked and the database was...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2023 at 7:21 pm
onetsql,
Nice link. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2023 at 2:26 pm
I did attempt to import your bacpac, ...
I'll likely never make the attempt on these forums because it's not permanent to this forum. If it goes away, any answer...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2023 at 2:11 pm
Created a table in such a way, each rowsize is one 8K page.
Now when I execute this
SELECT T.name as 'Table', ix.index_id, ix.[name] AS IndexName, ix.type_desc AS IndexType, [ips].[index_level],...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2023 at 2:00 pm
So what was your final problem and resolution?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2023 at 1:37 pm
Hi Jeff
Yeah vendor is aware of this issue. But get where you are coming from for sure.It was caused by a crappy import tool they wrote.. Really the records...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2023 at 1:02 am
I seriously wish you the best of luck. Get your QA/UAT started on checking for bad info/reporting/etc.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2023 at 7:56 pm
Personally, it was the DB Vendor's code that allowed the "duplicate" to begin with and I'd ask them rather than changing data that may have a substantial impact somewhere else. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2023 at 7:47 pm
That would happen if you did not have ord.Amount wrapped in the aggregate SUM function.
It should work w/ the query listed.
It can't... there's no ORDER_ID column in...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2023 at 7:21 pm
Viewing 15 posts - 1,591 through 1,605 (of 59,067 total)