Viewing 15 posts - 826 through 840 (of 1,192 total)
ChrisM@Work (9/25/2015)
mw112009 (9/25/2015)
Reason: EXISTS is just a another subquery that runs for each row that was fetched. Subqueries take time.
The LEFT JOIN will figure out the data set just...
September 25, 2015 at 9:44 am
You might be able to in the case of that exact value, by casting it as an appropriate numeric type. However, that is not a reliable technique. For example:
DECLARE
September 24, 2015 at 4:25 pm
mw112009 (9/24/2015)
Beleive me, the LEFT OUTER JOIN is faster.I deal with large tables and the "EXITS" make the query run for hours..
You likely have something else at play than just...
September 24, 2015 at 4:15 pm
Kristen-173977 (9/14/2015)
Jacob Wilkins (9/14/2015)
Well, he did say that the shrinking is of the log files, so that isn't contributing to index fragmentation, methinks 🙂
I agree. I'd diverted to start worrying...
September 14, 2015 at 1:11 pm
Kristen-173977 (9/14/2015)
krypto69 (9/14/2015)
I am running my weekly maintenance plans that use Ola's script for DBCC CHECKDB.
Naive question but does that include Index Rebuild, as well as CHECKDB?
krypto69 (9/14/2015)
September 14, 2015 at 11:21 am
Ed Wagner (9/11/2015)
Markus (9/11/2015)
try backing up to multiple files... 3...4... instead of 1 file.
Also, if you are SQL2008R2 or greater use...
September 11, 2015 at 12:38 pm
Just to confirm, it's running without errors but not actually replacing any characters?
Might be something like this: https://connect.microsoft.com/SQLServer/feedback/details/385082/replace-function-does-not-work-with-valid-unicode-characters-above-65500
Try using the explicit binary collation as in that workaround, i.e.:
UPDATE TABLE
SET DS...
September 11, 2015 at 9:18 am
Hugo Kornelis (9/11/2015)
Jacob Wilkins (9/10/2015)
September 11, 2015 at 8:30 am
There are a lot of factors involved in how to reduce the size of log files and whether you even should.
Ideally, I would say make a priority of reading this:...
September 10, 2015 at 4:12 pm
Should be able to REPLACE the NCHAR(65533).
Something like this:
DECLARE @UnicodeString NCHAR(100);
SET @UnicodeString=NCHAR(65533)+N'Hey, what''s that at the beginning?';
SELECT @UnicodeString;
SELECT REPLACE(@UnicodeString,NCHAR(65533),'');
Cheers!
September 10, 2015 at 3:45 pm
Jacob Wilkins (9/10/2015)
Hugo Kornelis (9/10/2015)
Jacob Wilkins (9/10/2015)
Ken Wymore (9/10/2015)
Interesting question. I was sure it would give an error.
Queries that already have a plan cached that uses the nonclustered index will...
September 10, 2015 at 3:30 pm
Hugo Kornelis (9/10/2015)
Jacob Wilkins (9/10/2015)
Ken Wymore (9/10/2015)
Interesting question. I was sure it would give an error.
Queries that already have a plan cached that uses the nonclustered index will throw an...
September 10, 2015 at 1:11 pm
Ken Wymore (9/10/2015)
Interesting question. I was sure it would give an error.
Queries that already have a plan cached that uses the nonclustered index will throw an error.
The bit of...
September 10, 2015 at 1:00 pm
The number of rows in the table and whether the query is parallelized are both completely irrelevant to lock partitioning. Microsoft's example to illustrate lock partitioning is on a table...
September 4, 2015 at 1:56 pm
Ah, thanks for posting that. I'd been having more trouble finding a 2008 instance than I'd expected.
So it seems 2008 (not R2) is the same as the others I've tested,...
September 4, 2015 at 1:08 pm
Viewing 15 posts - 826 through 840 (of 1,192 total)