Viewing 15 posts - 47,326 through 47,340 (of 59,095 total)
I probably wouldn't do a lot of "IF's" although those can be quite effective provided that it's not building dynamic SQL. A well formed WHERE clause with CASE statements...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2008 at 6:05 am
Lynn Pettis (11/10/2008)
Seems to me that a stored procedure, a temp table and a variation on the running count would give you what you need.What do you think, Jeff?
The data...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2008 at 5:58 am
krayknot (11/10/2008)
if you want i can forward that function on your email id.
Heh... post it here so we can all enjoy it. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2008 at 5:39 am
...and that still won't guarantee that the user can write to the DB. Oracle has it's own "system" views... if you want to see what privs a user has,...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2008 at 5:36 am
Mazharuddin is correct. The user won't necessarily be able to do anything... it just verifies that the user can connect. If you want to verify the user can...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2008 at 5:34 am
The best thing to do, if it can be done, is to use variables like the original code. Of course, the OR still needs to be fixed as I...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2008 at 5:28 am
Adam Hardy (11/10/2008)
Thanks for the input, but I think you may have miss-read my post, I said I was utilising triggers for data integrity tasks, not business rules....
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2008 at 5:20 am
Jack Corbett (11/4/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2008 at 5:07 am
Oh my... I just remembered where the heck such a requirement for all positive numbers may have come from... PeopleSoft software. Seems like the last folks that I knew...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2008 at 5:03 am
Be careful, Sue... having a fully dynamic WHERE clause is very suseptable to SQL Injection attacks if the code is exposed to the general public.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2008 at 4:57 am
You shouldn't ever bulk insert directly into the final table that already has rows in it. Bulk insert into a staging table first, check it for dupes, than then...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 10, 2008 at 9:37 pm
Jeff Moden (11/10/2008)
That sounds more like problems with a table variable. Why aren't you using a temp table, instead?
Heh... sorry... I forgot... you're happy with the code you have....
--Jeff Moden
Change is inevitable... Change for the better is not.
November 10, 2008 at 9:25 pm
Continued at the following... on the 2k forum...
http://www.sqlservercentral.com/Forums/Topic599997-169-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
November 10, 2008 at 9:08 pm
You've got me... I use OPENROWSET for that type of stuff. Or, better yet, I'll have Excel write an importable CSV when they close the spreadsheet.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 10, 2008 at 8:55 pm
ajaykini (11/10/2008)
I have developed a web based software for a Multi level Marketing Company where one member joins and then gets 2 members below him - one on the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 10, 2008 at 8:52 pm
Viewing 15 posts - 47,326 through 47,340 (of 59,095 total)