Viewing 15 posts - 46,186 through 46,200 (of 49,571 total)
Make sure that the users who use the appliction don't have rights to stop services (not SQL permissions, windows level permissions). Make sure no one but the server admins can...
June 19, 2008 at 6:11 am
Different join means a different execution plan. SQL probably generated one that doesn't have the same massive internal tables.
Can you post the plan with the outer join? I'd like to...
June 19, 2008 at 4:40 am
Vladan (6/18/2008)
The data types in Inserted are the same as in the actual table.
Good point. Would need 2 columns then. 1 a varchar that the insert puts the 'date' into,...
June 19, 2008 at 4:13 am
Service packs for which version of SQL? 7, 2000, 2005?
As for what differes, there's no single answer to that. Each of the service packs for each version fixes different things....
June 19, 2008 at 2:48 am
When you set up the trace, do you set it to write the trace to disk?
June 19, 2008 at 2:43 am
Could you explain a bit more what you want please?
Last modified in terms of data? Last modified in terms of schema? Something else?
June 19, 2008 at 1:10 am
You can do it via a SQL query.
ALTER DATABASE tempdb
MODIFY FILE (NAME = tempdev, FILENAME = < New directory>\tempdb.mdf');
GO
ALTER DATABASE tempdb
MODIFY FILE (NAME = templog, FILENAME =...
June 19, 2008 at 12:46 am
Ignoring memory for now...
Run performance monitor for an hour or so while the problems are occuring. Add the following counters:
Physical Disk:Avg sec/read
Physical Disk:Avg sec/write
SQL Server Buffer manager:Buffer cache hit ratio
SQL...
June 19, 2008 at 12:39 am
Bear in mind that using or posting brain dumps is against the rules of the exam (and a violation of the agreeemant that you accept upon writing the exam) and...
June 19, 2008 at 12:10 am
No. I didn't.
Will give it a shot when I get home, If I have a chance.
SQL shouldn't be doing the data type test before the actual insert. Instead...
June 18, 2008 at 8:09 am
It's not the number of rows. The query processor thinks there's a couple of cross joins happening.
Suggestion: Go carefull through the joined tables and make sure that all tables are...
June 18, 2008 at 8:06 am
The execution plan is warning of missing join predicates in a couple places. It thinks you have cartesian products forming
From the way the actual row count is increasing at points...
June 18, 2008 at 7:29 am
The reads have gone down, which is good. Has the CPU time also increased, or just the duration?
Did you run the query a couple times before taking measurements? If it...
June 18, 2008 at 7:15 am
Yes, it is. Write it properly and there won't be much of an impact.
Since the instead of fires before the data is inserted, you can't fire it only when...
June 18, 2008 at 7:11 am
Your first option uses correlated subqueries. It's a hidden row by row operation. It's gonna be slow, especially on larger result sets. The subqueries will run once for each row...
June 18, 2008 at 7:05 am
Viewing 15 posts - 46,186 through 46,200 (of 49,571 total)