Viewing 15 posts - 6,676 through 6,690 (of 59,091 total)
Yea, that is the problem with this one. It only lists the dbs since last server restart that have been accessed, I want an opposite list. In a SQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2020 at 1:21 pm
Just as a side note, depending on how often your columns are updated/modified, you can always split the string ahead of time using a permanent tally table like this:
Agreed. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2020 at 12:54 pm
This is awesome. worked great. you made my day Jeff. Always big fan of you.. 🙂
Glad to have been able to help. Thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2020 at 4:39 am
Here you go. DelimitedSplit8K made the changes very simple.
--****** This is for when the position matches, as well... ******
--===== Define what we're looking for.
...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2020 at 1:46 am
I changed the order by and it returned 12 records for the 1st month. I'm expecting 5 records for each month. Thank you.
SELECT DISTINCT t.Company,sales.[Month], sales.Sales
FROM...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2020 at 1:22 am
Heh... serendipity strikes. There's a pretty good article on all of this that was in an article in yesterday's MSSQLTips email. The link to the article I'm talking about is...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2020 at 1:16 am
My apologies... I missed the part about the "array position" in your original post. We can fix that but Split_String isn't going to work at all for that because (and...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2020 at 1:03 am
Yes, the login isn't correct. That's what the error is.
But I didn't change the login parameters. So I don't know why is working the 1st case...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2020 at 8:34 pm
sys.dm_db_index_usage_stats already has all the index usage for all databases and all tables inside it..
Careful now. If, for example, any database is totally unused, it my not show up...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2020 at 8:16 pm
p.p.s.
If anyone wants to do some testing of the method I posted or some other method, here's a 500,000 row test table like the OP said ("few hundred thousand") they...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2020 at 7:04 pm
p.s.
If you have to do such lookups a whole lot, it would help a whole lot if you materialized the NVP as a very narrow unique Clustered Index table and...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2020 at 6:26 pm
Ok... making the assumption that ID1 is actually supposed to be unique, here's the creation/population of the test table that I reformatted the way I normally would write such code...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2020 at 6:02 pm
Did you mean to have 2 entries in the StrHold table that have a "6" for ID1 or is that a typo???
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2020 at 5:24 pm
I'm not seeing any code attached to your last post. What code are you talking about being "attached"?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2020 at 11:41 pm
Have you actually looked at the code in Ola's script to see what the issue may be? It could be easier to fix your problem in his code than it...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2020 at 11:04 pm
Viewing 15 posts - 6,676 through 6,690 (of 59,091 total)