Viewing 15 posts - 5,776 through 5,790 (of 59,089 total)
I've never run across any "odd results" by using CHAR(1) in such a SELECT, yet. With that in mind, do you have an example of what happened so 1) we...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2021 at 3:56 pm
Awesome question, Steve!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2021 at 3:49 pm
That was an interesting question today! Learned something new!
As a bit of a sidebar, it will also seriously speed up code for things like REPLACE, especially for servers that...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2021 at 3:48 pm
When you run such code, everything is pretty much "server-centric" when it comes to drive letters. For example, you're referencing the "C:" drive in your code... when that executes on...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2021 at 3:42 pm
Thank you! First I've heard of a Tally table. I'm confused on one point in your discussion. You say,
The largest number in the Tally table should not be just...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2021 at 11:46 pm
It's completely dependent on the indexes. I know Minion lets you pick lists of indexes & break up the process. I suppose Ola's script must too. Do that. Do...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2021 at 7:03 pm
Yes, I also thought about it, but the following example shows it doesn't matter - SQL Server implicitly converts NULL to the correct type, no?
DECLARE @t...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2021 at 6:40 pm
Does "index disabling" blocks a table? Do we have any constraints regarding it?
No... disabling the index doesn't substantially block the table except for the time it takes to disable...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2021 at 6:36 pm
Sure. I have separate scripts for creating table and for creating indexes.
SET ANSI_PADDING ON
GO
CREATE NONCLUSTERED INDEX [IX_User_LastName] ON [dbo].[User]
(
[LastName] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2021 at 6:13 pm
Thanks for the cover, Thom. I should have posted the links like you did.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2021 at 6:10 pm
I was thinking the same thing but I've not yet seen it go parallel. That's most likely because I don't use it for much of anything because it does require...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2021 at 3:15 pm
Again, just to say it out loud... use such methods at your own risk because MS has stated that there is to guaranteed output order from STRING_SPLIT(). I've not run...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2021 at 5:31 am
For example, I have a table with very frequent inserts and there is high fragmentation. Is it advisable to create an index on such a table?
Can you post the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2021 at 2:25 am
Each restart, yes, but also failovers, detach/attach, all sorts of variation on that data. It is the one place to try to determine if indexes are in use, but,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2021 at 5:26 pm
For those of you that knew him, Gareth Swanepoel passed away on Friday - https://twitter.com/SQLBalls/status/1347722916700557319
He was a passionate member of the SQL community and a fellow speaker I've...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2021 at 5:21 pm
Viewing 15 posts - 5,776 through 5,790 (of 59,089 total)