Viewing 15 posts - 57,661 through 57,675 (of 59,101 total)
SELECT dbo.functionname(@parameter)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 10:10 pm
Job Requirements:
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 9:06 pm
Here's how to do it... you will need to replace "dbname" with the actual name of the database. You will need to do like wise with "servername". Once you've tested...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 8:29 pm
Why on Earth would you put the creation of a temp table in an explicit transaction? And, so far as exclusively locking the system tables when you use SELECT/INTO to...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 5:56 pm
You bet, Remi... we actually put the requirement in our "SQL Coding Standards" document so the Developers are made keenly aware of the problem. Since we do code reviews on...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 5:51 pm
Sreejith,
Yep... we had a bunch of these... they all worked fine until, one day... That's what's so insidious about it. Works fine until you reach some unknown tipping point and...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 5:48 pm
I'm with you there... one of my favorite sayings is "Anyone can make a mistake but to really mess things up, you need a computer." ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 6:44 am
Nope... it doesn't matter if they're 2 or 20,000... especially when someone posts as well as you do
Dunno... maybe I need some stronger...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 6:42 am
Can you post some sample data, hopefully in the form of INSERT statements, along with the CREATE statement for the table you're trying to get the data from, please?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 6:28 am
I wouldn't say "never"... they're pretty handy when making a temp table and, since no one but the current session can use the temp table, there's no concurrency issue to...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 6:21 am
Heh, heh.... mine are getting worse... old brain.
You hit the nail on the head about the scope thing... I was curious as to why you declared the variable external to...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 6:18 am
Off the beaten path a bit, Serqiy, but what happened to your number of posts? You were way up there and now you have less than 1000? What'd they do? Reset...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2006 at 10:14 pm
As usual, Remi did it absolutely correct in the first reply above...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2006 at 10:02 pm
Ohhh no, no, no... we ran into that little jem... "death by SQL"... pegged 4 cpus for two hours to do a lousy 2 minute update... THAT was repeatable with...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2006 at 9:58 pm
Dollars to donuts says that someone change the privs on a folder or deleted a user with the privs... did you do a search for the DLL to find out...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2006 at 9:49 pm
Viewing 15 posts - 57,661 through 57,675 (of 59,101 total)