Viewing 15 posts - 46 through 60 (of 327 total)
From BOL:
...You must have been granted CREATE FUNCTION permissions to create, alter, or drop user-defined functions. Users other than the owner must be granted EXECUTE permission on a function...
November 1, 2005 at 2:57 pm
If you are using sql sever 2005 then you should consider eliminating the read with (nolock) and start using Read committed snapshot.
Read committed snapshot will give you...
October 5, 2005 at 10:38 am
Here's an interesting article on error handling.
http://www.sommarskog.se/error-handling-II.html#presumptions
July 7, 2005 at 3:16 pm
If I did this correctly, after removing all the casts and sums your statement comes out to be
1 + 0 / 40
and of couse the 0 / 40...
June 30, 2005 at 7:20 am
As long as you're explaining things maybe you also need to explain what COBOL is?
June 29, 2005 at 12:35 pm
Even this old COBOL programmer agrees with you
June 29, 2005 at 11:09 am
Here's two very helpful articles on working with dates in sql server:
June 29, 2005 at 10:07 am
As dcpeterson stated earlier you will see the correct results if you move your "waitfor " to just after the INSERT but this has little to do with Repeatable Read.
With...
June 28, 2005 at 3:10 pm
You can (should) place a constraint on the column to ensure that the time portion is always 00:00:00.000. Then it will never be an issue.
June 28, 2005 at 11:28 am
The isolation level that will work for you in this situation is Serializable. This can be done with the SET statement or by using With (holdlock)
select col_padre from padre
June 28, 2005 at 11:02 am
How can you determine that IF his blood type IS NULL THEN NOT DELETING him is CORRECT?
Because if you treat NULL as unknown then the correct answer is...
June 28, 2005 at 10:16 am
Delete from Suspect_List
Where blood_type <> 'O'
If Mr. Smith's blood type has not yet been determined and is set to NULL then he will correctly NOT be deleted.
If Mr. Smith's unknown...
June 27, 2005 at 8:58 am
Viewing 15 posts - 46 through 60 (of 327 total)