Viewing 15 posts - 526 through 540 (of 616 total)
Greg I have to say that is probably one of the coolest things I have seen in awhile.
November 7, 2007 at 8:50 am
Here's my 2 cents
CREATE PROCEDURE dbo.usp_MoveItem(@id1 char(1), @direction bit)
-- @direction = 1move up
-- @direction = 0move down
AS
-- Declare my variables. Note used @id1 in procedure defintion
-- instead of...
November 7, 2007 at 8:48 am
The collation setting only affects the passwords in SQL 2000. In SQL 2005 the passwords are case sensative and there is no way to change it.
Kenneth
November 7, 2007 at 4:12 am
Its the fact that it can be automated. I've worked with too many developers where they tended not to update the headers. Since the extended properties can be...
November 6, 2007 at 9:49 pm
Oh don't get me wrong. I'm all for "Proper" documentation. I'm just more for accurate (and existing) documentation (I've delt with way to many developers)
November 6, 2007 at 8:57 pm
I agree but the nice thing about extended properties is that you can run queries on the information. For example sort by last update date. For that matter...
November 6, 2007 at 8:22 pm
Another option is to use extended properties. As part of your alter code .. say right after the final "go" enter an extended property for the SP with something...
November 6, 2007 at 3:18 pm
I would love to see it if you can find it.
November 6, 2007 at 2:19 pm
It depends on what you mean by encrypted. If it is truly encrypted
Ie looks something like this:
DTSRun /~Z0xDAC2174AE009BA9EAFDFE4F8C02C4D5E70E125E112D6ECC40408B206774CA90EA767DE8612443BCE01BF6BB84E7C9E08AA9DDA04FD11DED435F81A2BAD5B95367F58222BDD99DE29D1B4536486954C5C15FB84B234DA01877CEB543538196CD304B38C2983B8DC9947291BFBD3D7DAFAA763BFD72296FCE44C602BEE4FEF18DF494A4B94C2D4AB60130C125741945A475789A80C4CF59ABE1524613EB4397A63EFB70C9198248F7563B657DA7561F340BA561C61687A1ADC3FD72FADC09B76DE46358042E40C338F24D2F1
Then to the best of my knowledge there is no way...
November 6, 2007 at 1:43 pm
One other possiblity is that SQL 2005 passwords are case sensative. In 2000 by default it was case-insensative. If your users are used to case-insensative they may be...
November 6, 2007 at 1:05 pm
Your first problem is that Decimal(3,2) will hold at most 9.99. Based on your data you will never be able to store it in that field.
If on the other...
November 6, 2007 at 9:15 am
Maybe I'm missing something but it sounds like you are trying to import a value of 100,00000000001 into a field with the format 9.99?
Shouldn't you be using decimal (14,11) to...
November 6, 2007 at 7:41 am
Did removing the ' fix the problem? I tried creating an sp using your code and it worked just fine once I removed the extra '.
November 5, 2007 at 3:58 pm
Although come to think of it if you are going to generate a script to drop all of the foreign keys, truncate the tables, then restore the foreign keys it...
November 5, 2007 at 3:43 pm
Actually there is a way to do it .. sort of. I ran into this at a job where we were supporting a dozen or so version of the...
November 5, 2007 at 3:36 pm
Viewing 15 posts - 526 through 540 (of 616 total)