Viewing 15 posts - 55,006 through 55,020 (of 59,072 total)
This probably doesn't help, but the right way to do it would be to deny all users the ability to create procs and to follow a code promotion process.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 17, 2007 at 5:23 pm
Thanks for taking the time for the explanation, Rog...
But... being able to pass tables to stored procedures, with the understanding that you will have multiple tables with the same...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 17, 2007 at 7:19 am
Let us know what you finally come up with so that others may learn, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2007 at 7:55 am
Heh... did you try it?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2007 at 7:54 am
http://www.firstsql.com/tutor.htm
When you get done being a newbie, then practice answering question on this forum as Serqiy suggested. You also may want to take a peek at...
Remember...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2007 at 7:53 am
Sounds like you need an intro to SQL... here's a good overview...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2007 at 7:48 am
SELECT MIN(fName),Age
FROM yourtable
GROUP BY Age
Although not sure why you want to give the alphabetically earlier names such a break. Why do you need to do this?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2007 at 4:58 pm
Outage = perception
... or ...
Outage = contract stipulations
On the perception side, if you can't do your job because some system is down, I'd consider that an outage.
I won't get into...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2007 at 4:51 pm
Please post the query that you've tried, so far... I'm thinking all we need to do is change one of the joins to an outer join and use ISNULL(columnname,0) on...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2007 at 4:46 pm
PCQ,
It's kinda like asking us to fix your car without seeing the car. Please post the offending code and table structure along with maybe some sample data ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2007 at 4:43 pm
I guess BOL doesn't have a really simple explanation of what an INDEX SEEK is nor why it's better than an INDEX SCAN...
Basically, the name of each says it all......
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2007 at 9:03 am
But this is an example of what I'm talking about... this was first on the returns for Google when I searched for "CHART OF SYSTEM TABLES FOR SQL SERVER". ...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2007 at 8:43 am
This is one place where a "control loop" will help... write the code to only update a couple million at a time in a loop until everything has been updated. You'll be...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2007 at 8:18 pm
UPDATE: check col by col, if any change value exists, updated is performed with the following statement for any... |
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2007 at 8:10 pm
| This is a great advantage in parameter use... |
Why? Why do you need to pass a table as a...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2007 at 5:16 pm
Viewing 15 posts - 55,006 through 55,020 (of 59,072 total)