Viewing 15 posts - 256 through 270 (of 790 total)
I usually look for filegroups creeping over an arbitary threshold, in this case 90% full, with something along the lines of:
DECLARE @PctFullThreshold SMALLINT
SET @PctFullThreshold =...
Cheers,
- Mark
October 3, 2003 at 9:07 pm
I'm afraid you can't use a variable in this manner
Cheers,
- Mark
Cheers,
- Mark
October 2, 2003 at 5:12 pm
Steve,
Actually a table spreads itself across the filegroup to which it's assigned.
Jarretg,
I've seen this happen before, but not as radically as your example. It's mainly due to the order...
Cheers,
- Mark
October 2, 2003 at 4:30 pm
Back to barking up the "shrink" tree
.... maybe an explicit DBCC shrinkfile/shrinkdb after the 5am deletions will force the background ghost cleanup to do its...
Cheers,
- Mark
October 2, 2003 at 4:14 pm
So much for that theory.
How about a Maintenance Plan job (with "remove unused space") maybe scheduled for the wrong time of day. Or maybe some other scheduled shrink?
Cheers,
- Mark
Cheers,
- Mark
October 2, 2003 at 2:35 am
As well as removing "about" from the noise words list, I think you'll have to rebuild the FT catalogs.
While it's been in the noise words list, "about" has...
Cheers,
- Mark
October 2, 2003 at 2:29 am
Is the database set for autoshrink?
Cheers,
- Mark
Cheers,
- Mark
October 2, 2003 at 2:16 am
If your query plans are identical then I assume they're both (clustered) index scans.
I would suggest that the CASE statement is introducing additional CPU (try profiler to confirm or refute...
Cheers,
- Mark
September 28, 2003 at 3:35 pm
Yes, it would be a performance problem, but to what extent I can't gauge. It will be particularly inefficient if the primary key columns are volatile (ie. updated frequently)....
Cheers,
- Mark
September 28, 2003 at 3:18 pm
bj007,
Is customercode in fact a unicode column? (ie. nchar or nvarchar). If it's char, varchar or anything else then a conversion has to be done, so an index...
Cheers,
- Mark
September 23, 2003 at 3:59 pm
Hitendra,
When you have databases in full recovery mode (which it appears you do), it's important to schedule regular transaction log backups. This backs up and then truncates the inactive...
Cheers,
- Mark
September 22, 2003 at 12:26 am
I wouldn't rely too much on WITH ENCRYPTION for your truly top secret code. The encryption algorithm is fairly easily cracked. ![]()
Cheers,
- Mark
Edited by - mccork...
Cheers,
- Mark
September 21, 2003 at 10:50 pm
I've sent all my SQL 6.5 servers to the recycle bin, but I think the syntax is:
DUMP TRANSACTION YourDBName WITH NO_LOG
or
DUMP TRANSACTION YourDBName WITH TRUNCATE_ONLY, NO_LOG
If these fail, you might...
Cheers,
- Mark
September 20, 2003 at 8:22 pm
Over here I've seen companies use the MessageNet email-to-SMS service, and then set up Exchange entries pointing to the relevant STMP addresses (eg. 0414555555@messagenet.com.au). SQL Mail could then send to...
Cheers,
- Mark
September 18, 2003 at 9:49 pm
Phill,
tkc has indicated what /* various fields* / and /* various parameters */ look like.
I'm assuming they're quite longwinded.
Cheers,
- Mark
Cheers,
- Mark
September 18, 2003 at 9:31 pm
Viewing 15 posts - 256 through 270 (of 790 total)