Viewing 11 posts - 16 through 26 (of 26 total)
Your method should work just fine. You must have a bug in your recordset loop that's displaying the prices.
If you run the sample query in Query Analyzer, does it give...
August 26, 2002 at 10:35 am
Antares, you beat me to it. I was going to post this. It outputs the code to run rather than execing it directly so he can review it before running...
August 26, 2002 at 10:29 am
(This was in reply to scotttr, not Antares686).
That sounds like too much hassle to me. Why not just do this:
UPDATE mytable
SET col1 =...
August 26, 2002 at 10:23 am
Do the servers have different settings for the default index fill factor? That would do it, if you had a clustered index and the first server had a fixed small...
August 26, 2002 at 10:11 am
UPDATE mytable SET fullname = REPLACE(fullname, ',', ' ')
- Troy King
August 26, 2002 at 9:50 am
Yup, Brian, I'm pretty sure you and I are the same page<g>. I was actually responding originally to chrhedga, who said "...This is because the clustered index covers the entire...
August 26, 2002 at 9:43 am
I also had this error. Re-installing SQL sp2 fixed it.
August 26, 2002 at 9:10 am
But index seeks being possible doesn't mean that the clustered index pages contain every single value possible... clustered indexes contain pointers to the first value on a given table data...
August 26, 2002 at 8:59 am
My opinion would be to skip the languageids altogether. It's not like you'll have two Englishes or two Germans in the languages table. The space saved by inventing a languageid...
August 26, 2002 at 8:45 am
UNIONs are also valuable when you need to use more than a single index for a given query. Normally, a single select will only use a single index per table,...
August 26, 2002 at 8:30 am
Unless MS has changed how clustered indexes work, a clustered index cannot cover a query. At least the way it used to work, a clustered index is a pointer tree,...
August 26, 2002 at 8:21 am
Viewing 11 posts - 16 through 26 (of 26 total)