Viewing 15 posts - 5,806 through 5,820 (of 59,101 total)
We have a Transaction server writing records to SQL recording machine data. The process writes records every 15 minutes to a table from different equipment.
I'd take out the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2021 at 4:39 pm
Put your search words in another table.
SELECT t.*
FROM dbo.table1 AS t
WHERE EXISTS (SELECT * FROM dbo.table2 AS x WHERE t.Product...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2021 at 5:54 am
Execute this to see the fillfactor in use. You would expect 50% right?
DBCC SHOWCONTIG (tbl_user);
You are wrong. SQL Server uses 100% no matter what.
What happens if we rebuild the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2021 at 5:32 am
Thanks, Steve.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2021 at 1:02 am
Given that you've stated this multiple times with an assortment of different "magic" fillfactors -- 51, 61, 82, etc. -- I don't think it's a "nitpick" at all. So,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2021 at 11:59 pm
Since RedGate owns SQLServerCentral.com, a burning question comes to mind and that is, "What privs level does RedGate's "monitor" product require"?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2021 at 11:55 pm
I am thinking of using full text search, but full text search does not allow leading wildcard, a search for "phone" will not return any record. What can I...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2021 at 11:42 pm
If you have some indexes that have woefully low (less than 80% average percent of page fullness [page density]), then rebuild (NOT reorganize) them at 82% to...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2021 at 10:30 pm
Grant Fritchey wrote:Doggone it. Silly thing took me to an old post on the thread and I responded a second time. Sorry. I'll leave it up.
It's tough getting old.
Actually, it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2021 at 10:15 pm
I strongly recommend against that. If you're waiting for a 50-80 mix of fragmentation, you've already waited for most of the fragmentation to happen. This is now in the "why...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2021 at 10:10 pm
My favorite of all time actually has nothing to do with SQL Server. It was a post (wish I kept the link) about an HP printer tech that was trying...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2021 at 7:11 pm
Let us uphold our standard on this site, assumptions and speculations have no place on this top quality forums!
😎
Just have a look at this:
https://www.sqlservercentral.com/forums/topic/decimal-places-2#post-3828162
There are way too many threads...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2021 at 5:36 pm
...but they don't any action.
Of course not... they're too busy trying to meet a usually impossible schedule...
They say, we are busy with so many projects going on and...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2021 at 2:28 am
No. It is not "correct". The correct answer is "It Depends".
It depends both on the data in the table, they key column(s) you've selected for the Clustered and Non-Clustered indexes,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2021 at 1:41 am
If you want coded help, please see the article at the first link in my signature line below for one way to create "Readily Consumable Data".
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2021 at 1:35 am
Viewing 15 posts - 5,806 through 5,820 (of 59,101 total)