Viewing 15 posts - 271 through 285 (of 302 total)
The copy jobs task will say "successful" if it thinks there's nothing to do when it runs.
Edit this job step, go to advanced tab, setup an output file to log...
February 29, 2004 at 10:33 pm
Your drives & space on them are not factors.
Are you sure this is a problem? You can achieve equal target and total memory counter values by forcing it with the "use fixed memory...
February 27, 2004 at 12:22 am
Not an answer, just an opinion: I would think the key here would be how many different disk drives you have available (probably obfuscated by SAN in your case). I can't...
February 20, 2004 at 6:57 am
use 2nd computer to periodically run a small query like "select @@servername" If you get timeout, other error, or no result then send your alert.
While this was no so uncommon in...
February 20, 2004 at 5:49 am
Your use of name lookup functions will definitely hamper performance as compared to function-less approach based on joins. Maybe w/small DB and/or fast h/w you can tolerate this.
RBYoung is exactly right, best reply I've...
February 20, 2004 at 5:05 am
I like alzdba's approach better. If you used dynamic SQL to tried & implement this all in one query, then you'd need to grant SELECT rights on all the underlying...
February 20, 2004 at 4:56 am
Problem is this:
EXEC @Path = GetMySupportCategoryPath @ID
Your GetMySupportCategoryPath subroutine will return an integer return code, 0 in this case since you don't explicitly RETURN anything else.
The data that...
February 20, 2004 at 4:49 am
Last idea: maybe you used to have statistics that were out-of-date & inducing the optimizer to choose bad query plan, but these statistics were dropped when you dropped indexes manually?
My...
February 17, 2004 at 11:29 am
Ok, only way I know to speed this up is if you can alter the SQL being executed. You won't see this documented very much, and i fact will often...
February 17, 2004 at 5:46 am
Maybe. I think this is one of the most fun parts of the job.
It might turn out that you need to do the tuning in the sourcecode too (same place...
February 17, 2004 at 4:54 am
PS - best solution is leave timeout as-is and focus on speeding up whatever it is that's slow. We have very active 100GB db w/text data being inserted/updated/queried all day...
February 14, 2004 at 9:08 am
No way. ConnectTimeout controls just that "connection timeout." How long it takes to establish a connection, nothing to do with how long it takes to run a query. There are also remote...
February 13, 2004 at 11:58 am
What you need is "query timeout" or "command timeout". ADO Connection has "CommandTimeout" property, or ADO Command object has a "Timeout" property. Either increase these to larger value or set to...
February 13, 2004 at 10:32 am
inugroho is right on. Your original query does not look useful, you probably wanted to put the * on other side of the equals sign? Then inugroho's second ansi-92 query...
February 13, 2004 at 10:16 am
I am pretty sure no way Access knows what's going on inside you stored proc.
So what's left, maybe security issue? Is the owner of your store proc dbo? Try grant exec...
February 13, 2004 at 9:14 am
Viewing 15 posts - 271 through 285 (of 302 total)