Viewing 15 posts - 6,886 through 6,900 (of 7,616 total)
Steven Willis (1/24/2013)To prevent unexpected errors, you should validate your dates. And the ISDATE function is not a reliable method for such validation.
ISDATE() is reliable for what it claims to...
January 24, 2013 at 2:39 pm
Marius.D (1/24/2013)
TempDB seems to be always full, maybe I'll reboot first.. thanks!
Then you've got a second issue that needs addressed! 🙂
Increase the size of tempdb until you have "slack" except...
January 24, 2013 at 10:32 am
HowardW (1/24/2013)
ScottPletcher (1/24/2013)
HowardW (1/24/2013)
ScottPletcher (1/24/2013)
HowardW (1/24/2013)
There's no need to make the column persisted prior to indexing it.
That's not necessarily always true. You might persist a column if its...
January 24, 2013 at 10:30 am
HowardW (1/24/2013)
ScottPletcher (1/24/2013)
HowardW (1/24/2013)
There's no need to make the column persisted prior to indexing it.
That's not necessarily always true. You might persist a column if its requires significant...
January 24, 2013 at 10:08 am
You can use CASE w/i a GROUP BY.
You can also use CASE w/i a SUM to control which values get aggregated. For example:
SELECT
a, b,
...
January 24, 2013 at 9:45 am
HowardW (1/24/2013)
SQL* (1/23/2013)
While reading about Computed column if found that if we mentioned PERSISTED Key word while creating/altering table then we can create index. But i'm able to create...
January 24, 2013 at 9:42 am
IF and only if ABC.COLUMN2 is a (very) large column, and ABC.COLUMN1 is used by itself a lot, it might be worthwhile to keep both indexes.
You should also review sys.dm_db_index_usage_stats...
January 24, 2013 at 9:33 am
You need to get rid of the massive GROUP BY; you should be able to do the SUM() in a subquery rather than the main query, but I can't be...
January 24, 2013 at 9:26 am
AFAIK there's no any accurate way to do that.
I guess IF every caller used a different login or sql user, you could tell from that, but overall I think that's...
January 24, 2013 at 9:13 am
First, I assume you've all met all the oodles of restrictions for an indexed view; you might want to verify that using Books Online "CREATE INDEX", "Remarks", "Indexed Views" as...
January 24, 2013 at 9:09 am
declare @search_pattern_should_be varchar(100)
set @search_pattern_should_be = '%[[][[][%] SQL Server [%]]]%'
--example
select case when @string like '%[[][[][%] SQL Server [%]]]%'
then'Matched' else 'No...
January 24, 2013 at 8:51 am
I think EXISTS would be the clearest indication that you just want to know if a matching row exists, not retrieve data from that row. For example:
SELECT
...
January 24, 2013 at 8:39 am
You should also consider specifying "SORT_IN_TEMPDB = ON" on the creation. That usually saves a little space in the db, and, perhaps more importantly, often makes the final table...
January 23, 2013 at 4:43 pm
DBA_Dom (1/23/2013)
Or what...
January 23, 2013 at 3:41 pm
Perry Whittle (1/23/2013)
and all that's easier than a quick check in the dbo.sysjobhistory table??
Yes: which specific entry for "Job A" does one check in sysjobhistory?
The last one? What if...
January 23, 2013 at 11:25 am
Viewing 15 posts - 6,886 through 6,900 (of 7,616 total)