Viewing 15 posts - 58,006 through 58,020 (of 59,067 total)
Wow, Mark... that's quite the laudry list...
There are many solutions (and caveats as Tim pointed out) to your list of nice-to-haves... if you do a search on this site, I'm...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2006 at 2:48 pm
I don't have one but, rumor has it, that there are encryption tools on the Software Developers Kit disk that comes with SQL Server. Without a doubt, someone will post...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2006 at 2:38 pm
Good point... but you have to know what the Recovery Model is set to. If it's set to FULL, even SELECT INTO is logged. Again, don't take my word for...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2006 at 10:12 am
Never mind... here's the answer to that last question in my previous post...
http://support.microsoft.com/kb/153441/EN-US/
... and make sure that you read the part that says ...
NOTE: This problem does not...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2006 at 7:04 pm
I appologize if I repeat some of the previous posts but I think they might be worth repeating... and I believe John Marks referenced the same URL that I do...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2006 at 6:51 pm
I see why people come to the conclusion that you must use FLOAT as an input to functions... what people should say on funtions is that you must not use...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2006 at 7:17 am
Excellent reference, GP... though I'm not sure what you meant by "you have to use Float if your application need math functions". If you meant that you are inherently using...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2006 at 10:16 pm
Nope... massive deoderant failure on my part ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2006 at 8:48 pm
Sure, Mick... Sorry for the previous all too brief post...
First, let me tell you that the others are absolutely correct... SMALLDATETIME is rounded to the nearest minute and you should...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2006 at 7:50 am
Sorry, Tim... poor choice of words on my part.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2006 at 6:58 am
You are correct... cannot attach files... nicely formatted code. Welcome aboard!
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2006 at 10:48 pm
It's things like this that make me appreciate a good old fashioned IDENTITY column...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2006 at 10:25 pm
PW beat me to it... don't use float for anything, if you can help it. It's one of those "approximation" data types that are based on binary math.
Now, what...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2006 at 10:20 pm
I guess I don't understand why no-one liked Ryan's first solution with the -275 thingy (although I'm not sure it will withstand a Leap Year). It was very simple and...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2006 at 9:32 pm
You could easily turn this into a stored procedure or perhaps a table function...
--===== Define the input parameters
DECLARE @PropertyIDtoFind INT
DECLARE @MileageLimit DECIMAL(7,2)
SET @PropertyIDtoFind = 183297
SET...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2006 at 8:55 pm
Viewing 15 posts - 58,006 through 58,020 (of 59,067 total)