Viewing 15 posts - 256 through 270 (of 343 total)
In addition to the execution plan, there are a number of things you can do that will never be shown via tools...
* Use CONVERT() instead of CAST
* Use INT OR...
May 15, 2003 at 9:43 am
How about this...
Cut out the IF EXISTS STATEMENTS
SELECT 'Yesterday'....
WHERE <condition>
UNION ALL
SELECT 'Yesterday', 0, 0, 0
WHERE NOT EXISTS ( Yesterday condition )
UNION ALL
SELECT 'Last Week' ....
...
May 8, 2003 at 12:47 pm
John - I must be reading this wrong. Please help me understand.
It appears that the structure is
if exists ( select * from <table> where <timeframe condition )
SELECT...
May 8, 2003 at 10:12 am
We saw this problem when someone was using another application to view the data which was reading large amounts of data, but feeding the results to the display a little...
May 8, 2003 at 10:06 am
Some simple observatoions:
- It appears that you are setting the variable @nRowcount in the '[heaps of set statements]' if not, are you meaning @@ROWCOUNT?
- Since this is a...
May 8, 2003 at 9:57 am
Remember that using TOP and ORDER BY cause the entire query to run in the background even after the results have been returned.
Is it possible to create an index using...
May 2, 2003 at 10:52 am
Here are two approaches you might use. Since I don't know if you are using an INSERT statement directly or a stored procedure, please adjust the response accordingly.
1. ...
May 2, 2003 at 10:45 am
srinigk
There are so many variables it is hard to give a definitive answer. We have one database with over 110 million rows which performs consistently as it continues to...
April 29, 2003 at 9:18 am
We seem to see this problem whenever the database reaches a larger size and tries to automatically expand to accept new data. Depending on the volume of new data,...
April 28, 2003 at 2:07 pm
This seems to be different than it was with version 6.5. It took me a while to get used to in SQL 2000.
I personally prefer the compilation failure but...
April 17, 2003 at 4:15 pm
My understanding is this:
1) Blobs themselves don't cause corruption problems. Transaction handling and "chunking" need to be handled carefully, though.
2) Macro virus' are only problems when the macro is...
April 17, 2003 at 10:04 am
I can only speak for the hosting company that services one of my clients...
They create the databases with the owner as the login given to each client. The client...
April 17, 2003 at 9:53 am
You could also have a Country sorting table with two columns (Country and sortorder). For complete normalization, you could throw in an ID (for space consideration) and use that...
April 17, 2003 at 8:45 am
I am sure someone else has resolved this issue and can add information to avoid the problems we experienced. When we started to query across machines (using SQL Standard),...
April 17, 2003 at 8:41 am
jemmer,
Logged into query analyzer, execute this:
select so.name 'ProcName', su.name 'UserName'
from sysobjects so
inner join sysusers su on su.uid = so.uid
where so.type = 'P'
It would show you if...
April 14, 2003 at 8:37 am
Viewing 15 posts - 256 through 270 (of 343 total)