Viewing 15 posts - 51,556 through 51,570 (of 59,091 total)
While we're on the subject...
Thanks to all the folks in the military keeping all of us safe or keeping those that can't defend themselves safe... think of all the birthdays,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 5:34 pm
Yeaup... version control is a good thing even if you're the only one doing everything. It's saved my hiney a couple of times...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 5:23 pm
Maybe it's just me... but, in most cases, I find that "Business Intelligence" is an oxy-moron with emphasis on the word "moron" 😉 ...
I worked for a Fortune 100...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 6:30 am
Part I is a good (possibly too brief) introduction to EAV's 😉 Like the other's I'm looking forward to Part II.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 6:03 am
Nice short to-the-point article on some very useful information... thanks!
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 5:56 am
There are several system functions to help you in the area of user names...
USER
USER_ID()
USER_NAME() -- Same as CURRENT_USER
SESSION_USER
SYSTEM_USER -- Probably the one you're looking for.
Using the @@SPID system...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 5:50 am
Great description, Pcplayer... that one is a bit out of scope for things I've done, but between the description and the error messages you've shown, someone is bound to help......
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 5:39 am
molecule_kaab (3/23/2008)
I wonder that if I use TRIGGER, can it tell which field is modified.
I want to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 23, 2008 at 2:59 pm
A better question would be... what is it that you're actually trying to do using OLE Automation?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 23, 2008 at 2:42 pm
I agree with Matt and Barry... a permanent date table would be much faster than any other method. Lot's more convenient, too, because all the dates are always available....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 23, 2008 at 2:27 pm
ace (3/22/2008)
I appreciate...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 23, 2008 at 2:01 pm
Thanks... lots of folks don't know when I'm joking or not...
On the serious side, the really neat thing about the Developer's edition is that every developer can have it on...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 22, 2008 at 12:07 pm
If you're gonna use a compare tool to promote from Dev to Prod, you might as well just give the developers full access to Prod... unless you do a code...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 22, 2008 at 11:08 am
If you would take the data you originally posted and put it and a simple table definition into the form that Lynn asked you to, that would be great 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 22, 2008 at 10:20 am
ksullivan (3/22/2008)
There is no need to include upper() in the where clause. TSQL is not case sensitive.
Not quite true... the default is to setup SQL Server so that it...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 22, 2008 at 10:14 am
Viewing 15 posts - 51,556 through 51,570 (of 59,091 total)