I am updating data from a smaller linked table into a larger table (SQL
server 2K sp4, Win server 2k3 sp1) (data which had been inserted
previously). The update now looks like:
UPDATE tableA
SET colx = (select colx FROM linkedtableB rem
WHERE rem.pkcol = tableA.pkcol),
coly = (select coly FROM linkedtableB rem
WHERE rem.pkcol = tableA.pkcol)
WHERE EXISTS (SELECT * FROM linkedtableB as rem
WHERE rem.pkcol = tableA.pkcol)
This seems to run an inordinately long time (in excess of 1hr + for
this one table, and I have to update 40 more tables). My question it,
what would be a more effiecient way to update this data? My reasoning
for updating this data is, while doing the insert earlier, I may have
gathered partial data during an operation, thus requiring an update at
some later point.
Any insight into a better solution would be greatly appriciated.
Daniel
danielp
try this one
UPDATE tableA SET colx =rem.colx , coly =rem.coly FROM linkedtableB rem
JOIN tableA ON
rem.pkcol = tableA.pkcol
"danielp" <danielsmith611@.gmail.com> wrote in message
news:1162310539.241683.96330@.e3g2000cwe.googlegrou ps.com...
>I am updating data from a smaller linked table into a larger table (SQL
> server 2K sp4, Win server 2k3 sp1) (data which had been inserted
> previously). The update now looks like:
> UPDATE tableA
> SET colx = (select colx FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol),
> coly = (select coly FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol)
> WHERE EXISTS (SELECT * FROM linkedtableB as rem
> WHERE rem.pkcol = tableA.pkcol)
> This seems to run an inordinately long time (in excess of 1hr + for
> this one table, and I have to update 40 more tables). My question it,
> what would be a more effiecient way to update this data? My reasoning
> for updating this data is, while doing the insert earlier, I may have
> gathered partial data during an operation, thus requiring an update at
> some later point.
> Any insight into a better solution would be greatly appriciated.
> Daniel
>
|||Hi Daniel
Try
UPDATE A
SET colx = B.colx
coly = B.coly
FROM tableA A
JOIN linkedtableB B ON B.pkcol = A.pkcol
John
"danielp" wrote:
> I am updating data from a smaller linked table into a larger table (SQL
> server 2K sp4, Win server 2k3 sp1) (data which had been inserted
> previously). The update now looks like:
> UPDATE tableA
> SET colx = (select colx FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol),
> coly = (select coly FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol)
> WHERE EXISTS (SELECT * FROM linkedtableB as rem
> WHERE rem.pkcol = tableA.pkcol)
> This seems to run an inordinately long time (in excess of 1hr + for
> this one table, and I have to update 40 more tables). My question it,
> what would be a more effiecient way to update this data? My reasoning
> for updating this data is, while doing the insert earlier, I may have
> gathered partial data during an operation, thus requiring an update at
> some later point.
> Any insight into a better solution would be greatly appriciated.
> Daniel
>
|||I missed out a comma!
UPDATE A
SET colx = B.colx,
coly = B.coly
FROM tableA A
JOIN linkedtableB B ON B.pkcol = A.pkcol
John
"John Bell" wrote:
[vbcol=seagreen]
> Hi Daniel
> Try
> UPDATE A
> SET colx = B.colx
> coly = B.coly
> FROM tableA A
> JOIN linkedtableB B ON B.pkcol = A.pkcol
> John
> "danielp" wrote:
|||Thanks Uri and John!
John Bell wrote:[vbcol=seagreen]
> I missed out a comma!
> UPDATE A
> SET colx = B.colx,
> coly = B.coly
> FROM tableA A
> JOIN linkedtableB B ON B.pkcol = A.pkcol
> John
> "John Bell" wrote:
Showing posts with label larger. Show all posts
Showing posts with label larger. Show all posts
Wednesday, March 28, 2012
More effiect update from linked server
I am updating data from a smaller linked table into a larger table (SQL
server 2K sp4, Win server 2k3 sp1) (data which had been inserted
previously). The update now looks like:
UPDATE tableA
SET colx = (select colx FROM linkedtableB rem
WHERE rem.pkcol = tableA.pkcol),
coly = (select coly FROM linkedtableB rem
WHERE rem.pkcol = tableA.pkcol)
WHERE EXISTS (SELECT * FROM linkedtableB as rem
WHERE rem.pkcol = tableA.pkcol)
This seems to run an inordinately long time (in excess of 1hr + for
this one table, and I have to update 40 more tables). My question it,
what would be a more effiecient way to update this data? My reasoning
for updating this data is, while doing the insert earlier, I may have
gathered partial data during an operation, thus requiring an update at
some later point.
Any insight into a better solution would be greatly appriciated.
Danieldanielp
try this one
UPDATE tableA SET colx =rem.colx , coly =rem.coly FROM linkedtableB rem
JOIN tableA ON
rem.pkcol = tableA.pkcol
"danielp" <danielsmith611@.gmail.com> wrote in message
news:1162310539.241683.96330@.e3g2000cwe.googlegroups.com...
>I am updating data from a smaller linked table into a larger table (SQL
> server 2K sp4, Win server 2k3 sp1) (data which had been inserted
> previously). The update now looks like:
> UPDATE tableA
> SET colx = (select colx FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol),
> coly = (select coly FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol)
> WHERE EXISTS (SELECT * FROM linkedtableB as rem
> WHERE rem.pkcol = tableA.pkcol)
> This seems to run an inordinately long time (in excess of 1hr + for
> this one table, and I have to update 40 more tables). My question it,
> what would be a more effiecient way to update this data? My reasoning
> for updating this data is, while doing the insert earlier, I may have
> gathered partial data during an operation, thus requiring an update at
> some later point.
> Any insight into a better solution would be greatly appriciated.
> Daniel
>|||Hi Daniel
Try
UPDATE A
SET colx = B.colx
coly = B.coly
FROM tableA A
JOIN linkedtableB B ON B.pkcol = A.pkcol
John
"danielp" wrote:
> I am updating data from a smaller linked table into a larger table (SQL
> server 2K sp4, Win server 2k3 sp1) (data which had been inserted
> previously). The update now looks like:
> UPDATE tableA
> SET colx = (select colx FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol),
> coly = (select coly FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol)
> WHERE EXISTS (SELECT * FROM linkedtableB as rem
> WHERE rem.pkcol = tableA.pkcol)
> This seems to run an inordinately long time (in excess of 1hr + for
> this one table, and I have to update 40 more tables). My question it,
> what would be a more effiecient way to update this data? My reasoning
> for updating this data is, while doing the insert earlier, I may have
> gathered partial data during an operation, thus requiring an update at
> some later point.
> Any insight into a better solution would be greatly appriciated.
> Daniel
>|||I missed out a comma!
UPDATE A
SET colx = B.colx,
coly = B.coly
FROM tableA A
JOIN linkedtableB B ON B.pkcol = A.pkcol
John
"John Bell" wrote:
[vbcol=seagreen]
> Hi Daniel
> Try
> UPDATE A
> SET colx = B.colx
> coly = B.coly
> FROM tableA A
> JOIN linkedtableB B ON B.pkcol = A.pkcol
> John
> "danielp" wrote:
>|||Thanks Uri and John!
John Bell wrote:[vbcol=seagreen]
> I missed out a comma!
> UPDATE A
> SET colx = B.colx,
> coly = B.coly
> FROM tableA A
> JOIN linkedtableB B ON B.pkcol = A.pkcol
> John
> "John Bell" wrote:
>
server 2K sp4, Win server 2k3 sp1) (data which had been inserted
previously). The update now looks like:
UPDATE tableA
SET colx = (select colx FROM linkedtableB rem
WHERE rem.pkcol = tableA.pkcol),
coly = (select coly FROM linkedtableB rem
WHERE rem.pkcol = tableA.pkcol)
WHERE EXISTS (SELECT * FROM linkedtableB as rem
WHERE rem.pkcol = tableA.pkcol)
This seems to run an inordinately long time (in excess of 1hr + for
this one table, and I have to update 40 more tables). My question it,
what would be a more effiecient way to update this data? My reasoning
for updating this data is, while doing the insert earlier, I may have
gathered partial data during an operation, thus requiring an update at
some later point.
Any insight into a better solution would be greatly appriciated.
Danieldanielp
try this one
UPDATE tableA SET colx =rem.colx , coly =rem.coly FROM linkedtableB rem
JOIN tableA ON
rem.pkcol = tableA.pkcol
"danielp" <danielsmith611@.gmail.com> wrote in message
news:1162310539.241683.96330@.e3g2000cwe.googlegroups.com...
>I am updating data from a smaller linked table into a larger table (SQL
> server 2K sp4, Win server 2k3 sp1) (data which had been inserted
> previously). The update now looks like:
> UPDATE tableA
> SET colx = (select colx FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol),
> coly = (select coly FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol)
> WHERE EXISTS (SELECT * FROM linkedtableB as rem
> WHERE rem.pkcol = tableA.pkcol)
> This seems to run an inordinately long time (in excess of 1hr + for
> this one table, and I have to update 40 more tables). My question it,
> what would be a more effiecient way to update this data? My reasoning
> for updating this data is, while doing the insert earlier, I may have
> gathered partial data during an operation, thus requiring an update at
> some later point.
> Any insight into a better solution would be greatly appriciated.
> Daniel
>|||Hi Daniel
Try
UPDATE A
SET colx = B.colx
coly = B.coly
FROM tableA A
JOIN linkedtableB B ON B.pkcol = A.pkcol
John
"danielp" wrote:
> I am updating data from a smaller linked table into a larger table (SQL
> server 2K sp4, Win server 2k3 sp1) (data which had been inserted
> previously). The update now looks like:
> UPDATE tableA
> SET colx = (select colx FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol),
> coly = (select coly FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol)
> WHERE EXISTS (SELECT * FROM linkedtableB as rem
> WHERE rem.pkcol = tableA.pkcol)
> This seems to run an inordinately long time (in excess of 1hr + for
> this one table, and I have to update 40 more tables). My question it,
> what would be a more effiecient way to update this data? My reasoning
> for updating this data is, while doing the insert earlier, I may have
> gathered partial data during an operation, thus requiring an update at
> some later point.
> Any insight into a better solution would be greatly appriciated.
> Daniel
>|||I missed out a comma!
UPDATE A
SET colx = B.colx,
coly = B.coly
FROM tableA A
JOIN linkedtableB B ON B.pkcol = A.pkcol
John
"John Bell" wrote:
[vbcol=seagreen]
> Hi Daniel
> Try
> UPDATE A
> SET colx = B.colx
> coly = B.coly
> FROM tableA A
> JOIN linkedtableB B ON B.pkcol = A.pkcol
> John
> "danielp" wrote:
>|||Thanks Uri and John!
John Bell wrote:[vbcol=seagreen]
> I missed out a comma!
> UPDATE A
> SET colx = B.colx,
> coly = B.coly
> FROM tableA A
> JOIN linkedtableB B ON B.pkcol = A.pkcol
> John
> "John Bell" wrote:
>
More effiect update from linked server
I am updating data from a smaller linked table into a larger table (SQL
server 2K sp4, Win server 2k3 sp1) (data which had been inserted
previously). The update now looks like:
UPDATE tableA
SET colx = (select colx FROM linkedtableB rem
WHERE rem.pkcol = tableA.pkcol),
coly = (select coly FROM linkedtableB rem
WHERE rem.pkcol = tableA.pkcol)
WHERE EXISTS (SELECT * FROM linkedtableB as rem
WHERE rem.pkcol = tableA.pkcol)
This seems to run an inordinately long time (in excess of 1hr + for
this one table, and I have to update 40 more tables). My question it,
what would be a more effiecient way to update this data? My reasoning
for updating this data is, while doing the insert earlier, I may have
gathered partial data during an operation, thus requiring an update at
some later point.
Any insight into a better solution would be greatly appriciated.
Danieldanielp
try this one
UPDATE tableA SET colx =rem.colx , coly =rem.coly FROM linkedtableB rem
JOIN tableA ON
rem.pkcol = tableA.pkcol
"danielp" <danielsmith611@.gmail.com> wrote in message
news:1162310539.241683.96330@.e3g2000cwe.googlegroups.com...
>I am updating data from a smaller linked table into a larger table (SQL
> server 2K sp4, Win server 2k3 sp1) (data which had been inserted
> previously). The update now looks like:
> UPDATE tableA
> SET colx = (select colx FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol),
> coly = (select coly FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol)
> WHERE EXISTS (SELECT * FROM linkedtableB as rem
> WHERE rem.pkcol = tableA.pkcol)
> This seems to run an inordinately long time (in excess of 1hr + for
> this one table, and I have to update 40 more tables). My question it,
> what would be a more effiecient way to update this data? My reasoning
> for updating this data is, while doing the insert earlier, I may have
> gathered partial data during an operation, thus requiring an update at
> some later point.
> Any insight into a better solution would be greatly appriciated.
> Daniel
>|||Hi Daniel
Try
UPDATE A
SET colx = B.colx
coly = B.coly
FROM tableA A
JOIN linkedtableB B ON B.pkcol = A.pkcol
John
"danielp" wrote:
> I am updating data from a smaller linked table into a larger table (SQL
> server 2K sp4, Win server 2k3 sp1) (data which had been inserted
> previously). The update now looks like:
> UPDATE tableA
> SET colx = (select colx FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol),
> coly = (select coly FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol)
> WHERE EXISTS (SELECT * FROM linkedtableB as rem
> WHERE rem.pkcol = tableA.pkcol)
> This seems to run an inordinately long time (in excess of 1hr + for
> this one table, and I have to update 40 more tables). My question it,
> what would be a more effiecient way to update this data? My reasoning
> for updating this data is, while doing the insert earlier, I may have
> gathered partial data during an operation, thus requiring an update at
> some later point.
> Any insight into a better solution would be greatly appriciated.
> Daniel
>|||I missed out a comma!
UPDATE A
SET colx = B.colx,
coly = B.coly
FROM tableA A
JOIN linkedtableB B ON B.pkcol = A.pkcol
John
"John Bell" wrote:
> Hi Daniel
> Try
> UPDATE A
> SET colx = B.colx
> coly = B.coly
> FROM tableA A
> JOIN linkedtableB B ON B.pkcol = A.pkcol
> John
> "danielp" wrote:
> > I am updating data from a smaller linked table into a larger table (SQL
> > server 2K sp4, Win server 2k3 sp1) (data which had been inserted
> > previously). The update now looks like:
> >
> > UPDATE tableA
> > SET colx = (select colx FROM linkedtableB rem
> > WHERE rem.pkcol = tableA.pkcol),
> > coly = (select coly FROM linkedtableB rem
> > WHERE rem.pkcol = tableA.pkcol)
> > WHERE EXISTS (SELECT * FROM linkedtableB as rem
> > WHERE rem.pkcol = tableA.pkcol)
> >
> > This seems to run an inordinately long time (in excess of 1hr + for
> > this one table, and I have to update 40 more tables). My question it,
> > what would be a more effiecient way to update this data? My reasoning
> > for updating this data is, while doing the insert earlier, I may have
> > gathered partial data during an operation, thus requiring an update at
> > some later point.
> >
> > Any insight into a better solution would be greatly appriciated.
> >
> > Daniel
> >
> >|||Thanks Uri and John!
John Bell wrote:
> I missed out a comma!
> UPDATE A
> SET colx = B.colx,
> coly = B.coly
> FROM tableA A
> JOIN linkedtableB B ON B.pkcol = A.pkcol
> John
> "John Bell" wrote:
> > Hi Daniel
> >
> > Try
> >
> > UPDATE A
> > SET colx = B.colx
> > coly = B.coly
> > FROM tableA A
> > JOIN linkedtableB B ON B.pkcol = A.pkcol
> >
> > John
> >
> > "danielp" wrote:
> >
> > > I am updating data from a smaller linked table into a larger table (SQL
> > > server 2K sp4, Win server 2k3 sp1) (data which had been inserted
> > > previously). The update now looks like:
> > >
> > > UPDATE tableA
> > > SET colx = (select colx FROM linkedtableB rem
> > > WHERE rem.pkcol = tableA.pkcol),
> > > coly = (select coly FROM linkedtableB rem
> > > WHERE rem.pkcol = tableA.pkcol)
> > > WHERE EXISTS (SELECT * FROM linkedtableB as rem
> > > WHERE rem.pkcol = tableA.pkcol)
> > >
> > > This seems to run an inordinately long time (in excess of 1hr + for
> > > this one table, and I have to update 40 more tables). My question it,
> > > what would be a more effiecient way to update this data? My reasoning
> > > for updating this data is, while doing the insert earlier, I may have
> > > gathered partial data during an operation, thus requiring an update at
> > > some later point.
> > >
> > > Any insight into a better solution would be greatly appriciated.
> > >
> > > Daniel
> > >
> > >sql
server 2K sp4, Win server 2k3 sp1) (data which had been inserted
previously). The update now looks like:
UPDATE tableA
SET colx = (select colx FROM linkedtableB rem
WHERE rem.pkcol = tableA.pkcol),
coly = (select coly FROM linkedtableB rem
WHERE rem.pkcol = tableA.pkcol)
WHERE EXISTS (SELECT * FROM linkedtableB as rem
WHERE rem.pkcol = tableA.pkcol)
This seems to run an inordinately long time (in excess of 1hr + for
this one table, and I have to update 40 more tables). My question it,
what would be a more effiecient way to update this data? My reasoning
for updating this data is, while doing the insert earlier, I may have
gathered partial data during an operation, thus requiring an update at
some later point.
Any insight into a better solution would be greatly appriciated.
Danieldanielp
try this one
UPDATE tableA SET colx =rem.colx , coly =rem.coly FROM linkedtableB rem
JOIN tableA ON
rem.pkcol = tableA.pkcol
"danielp" <danielsmith611@.gmail.com> wrote in message
news:1162310539.241683.96330@.e3g2000cwe.googlegroups.com...
>I am updating data from a smaller linked table into a larger table (SQL
> server 2K sp4, Win server 2k3 sp1) (data which had been inserted
> previously). The update now looks like:
> UPDATE tableA
> SET colx = (select colx FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol),
> coly = (select coly FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol)
> WHERE EXISTS (SELECT * FROM linkedtableB as rem
> WHERE rem.pkcol = tableA.pkcol)
> This seems to run an inordinately long time (in excess of 1hr + for
> this one table, and I have to update 40 more tables). My question it,
> what would be a more effiecient way to update this data? My reasoning
> for updating this data is, while doing the insert earlier, I may have
> gathered partial data during an operation, thus requiring an update at
> some later point.
> Any insight into a better solution would be greatly appriciated.
> Daniel
>|||Hi Daniel
Try
UPDATE A
SET colx = B.colx
coly = B.coly
FROM tableA A
JOIN linkedtableB B ON B.pkcol = A.pkcol
John
"danielp" wrote:
> I am updating data from a smaller linked table into a larger table (SQL
> server 2K sp4, Win server 2k3 sp1) (data which had been inserted
> previously). The update now looks like:
> UPDATE tableA
> SET colx = (select colx FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol),
> coly = (select coly FROM linkedtableB rem
> WHERE rem.pkcol = tableA.pkcol)
> WHERE EXISTS (SELECT * FROM linkedtableB as rem
> WHERE rem.pkcol = tableA.pkcol)
> This seems to run an inordinately long time (in excess of 1hr + for
> this one table, and I have to update 40 more tables). My question it,
> what would be a more effiecient way to update this data? My reasoning
> for updating this data is, while doing the insert earlier, I may have
> gathered partial data during an operation, thus requiring an update at
> some later point.
> Any insight into a better solution would be greatly appriciated.
> Daniel
>|||I missed out a comma!
UPDATE A
SET colx = B.colx,
coly = B.coly
FROM tableA A
JOIN linkedtableB B ON B.pkcol = A.pkcol
John
"John Bell" wrote:
> Hi Daniel
> Try
> UPDATE A
> SET colx = B.colx
> coly = B.coly
> FROM tableA A
> JOIN linkedtableB B ON B.pkcol = A.pkcol
> John
> "danielp" wrote:
> > I am updating data from a smaller linked table into a larger table (SQL
> > server 2K sp4, Win server 2k3 sp1) (data which had been inserted
> > previously). The update now looks like:
> >
> > UPDATE tableA
> > SET colx = (select colx FROM linkedtableB rem
> > WHERE rem.pkcol = tableA.pkcol),
> > coly = (select coly FROM linkedtableB rem
> > WHERE rem.pkcol = tableA.pkcol)
> > WHERE EXISTS (SELECT * FROM linkedtableB as rem
> > WHERE rem.pkcol = tableA.pkcol)
> >
> > This seems to run an inordinately long time (in excess of 1hr + for
> > this one table, and I have to update 40 more tables). My question it,
> > what would be a more effiecient way to update this data? My reasoning
> > for updating this data is, while doing the insert earlier, I may have
> > gathered partial data during an operation, thus requiring an update at
> > some later point.
> >
> > Any insight into a better solution would be greatly appriciated.
> >
> > Daniel
> >
> >|||Thanks Uri and John!
John Bell wrote:
> I missed out a comma!
> UPDATE A
> SET colx = B.colx,
> coly = B.coly
> FROM tableA A
> JOIN linkedtableB B ON B.pkcol = A.pkcol
> John
> "John Bell" wrote:
> > Hi Daniel
> >
> > Try
> >
> > UPDATE A
> > SET colx = B.colx
> > coly = B.coly
> > FROM tableA A
> > JOIN linkedtableB B ON B.pkcol = A.pkcol
> >
> > John
> >
> > "danielp" wrote:
> >
> > > I am updating data from a smaller linked table into a larger table (SQL
> > > server 2K sp4, Win server 2k3 sp1) (data which had been inserted
> > > previously). The update now looks like:
> > >
> > > UPDATE tableA
> > > SET colx = (select colx FROM linkedtableB rem
> > > WHERE rem.pkcol = tableA.pkcol),
> > > coly = (select coly FROM linkedtableB rem
> > > WHERE rem.pkcol = tableA.pkcol)
> > > WHERE EXISTS (SELECT * FROM linkedtableB as rem
> > > WHERE rem.pkcol = tableA.pkcol)
> > >
> > > This seems to run an inordinately long time (in excess of 1hr + for
> > > this one table, and I have to update 40 more tables). My question it,
> > > what would be a more effiecient way to update this data? My reasoning
> > > for updating this data is, while doing the insert earlier, I may have
> > > gathered partial data during an operation, thus requiring an update at
> > > some later point.
> > >
> > > Any insight into a better solution would be greatly appriciated.
> > >
> > > Daniel
> > >
> > >sql
Saturday, February 25, 2012
Money type limitation
Does anyone know if Microsoft is planning to expand sql server Money
data type to larger what it is in sql server 2000; that is larger than
922,337,203,685,477.5807?
Thanks
HilalI haven't heard of such plans. You can always request at sqlwish@.microsoft.com. Or use NUMERIC
instead.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Hilal Issa" <hilal@.edm.com.lb> wrote in message news:u9ak8h9tDHA.2340@.TK2MSFTNGP12.phx.gbl...
> Does anyone know if Microsoft is planning to expand sql server Money
> data type to larger what it is in sql server 2000; that is larger than
> 922,337,203,685,477.5807?
> Thanks
> Hilal
>|||I don't know about future versions but if you want values larger than that
today use DECIMAL/NUMERIC which handles up to 38 digits preceision.
--
David Portas
--
Please reply only to the newsgroup
--
"Hilal Issa" <hilal@.edm.com.lb> wrote in message
news:u9ak8h9tDHA.2340@.TK2MSFTNGP12.phx.gbl...
> Does anyone know if Microsoft is planning to expand sql server Money
> data type to larger what it is in sql server 2000; that is larger than
> 922,337,203,685,477.5807?
> Thanks
> Hilal
>|||Thanks for the replies.
I will send an e-mail to sqlwish@.microsoft.com as Tibor suggested.
In fact, money data type would enough except in some cases where some values
might go beyond its boundaries; ex.: I have a table with 3 fields Qty, Unit
Amount and SubTotal (=Qty * Unit Amount). If we set Qty = 9999999 (seven
9's) and Unit Price = 99999999 (eight 9's)and Now calculate SubTotal = Qty *
Unit Amount, an overflow error is generated.
Indeed, I was trying converting all my fields using money datatype to
Decimal (38, 5) that is allowing 5 decimal places. I did not finish testing
with it yet. But I am guessing from now that I will have this problem with
wider range. Float (up to 1.79E + 308) would have been great but its
floating issue is not good at all in my case.
Best Regards
Hilal
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:SPidnZLuAOq5aleiRVn-hg@.giganews.com...
> I don't know about future versions but if you want values larger than that
> today use DECIMAL/NUMERIC which handles up to 38 digits preceision.
> --
> David Portas
> --
> Please reply only to the newsgroup
> --
> "Hilal Issa" <hilal@.edm.com.lb> wrote in message
> news:u9ak8h9tDHA.2340@.TK2MSFTNGP12.phx.gbl...
> > Does anyone know if Microsoft is planning to expand sql server Money
> > data type to larger what it is in sql server 2000; that is larger than
> > 922,337,203,685,477.5807?
> >
> > Thanks
> >
> > Hilal
> >
> >
>|||A bigger range for a money datatype is rediculous. Even the biggest
budget of the biggest country will not exceed 900 trillion.
I would suggest you simply handle any overflows. Who is going to spend
900 trillion dollars in your shop by buying 10 million units that cost
100 million dollars each? That just doesn't make sense.
My 5 cents,
Gert-Jan
Hilal Issa wrote:
> Thanks for the replies.
> I will send an e-mail to sqlwish@.microsoft.com as Tibor suggested.
> In fact, money data type would enough except in some cases where some values
> might go beyond its boundaries; ex.: I have a table with 3 fields Qty, Unit
> Amount and SubTotal (=Qty * Unit Amount). If we set Qty = 9999999 (seven
> 9's) and Unit Price = 99999999 (eight 9's)and Now calculate SubTotal = Qty *
> Unit Amount, an overflow error is generated.
> Indeed, I was trying converting all my fields using money datatype to
> Decimal (38, 5) that is allowing 5 decimal places. I did not finish testing
> with it yet. But I am guessing from now that I will have this problem with
> wider range. Float (up to 1.79E + 308) would have been great but its
> floating issue is not good at all in my case.
> Best Regards
> Hilal
> "David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
> news:SPidnZLuAOq5aleiRVn-hg@.giganews.com...
> > I don't know about future versions but if you want values larger than that
> > today use DECIMAL/NUMERIC which handles up to 38 digits preceision.
> >
> > --
> > David Portas
> > --
> > Please reply only to the newsgroup
> > --
> >
> > "Hilal Issa" <hilal@.edm.com.lb> wrote in message
> > news:u9ak8h9tDHA.2340@.TK2MSFTNGP12.phx.gbl...
> > > Does anyone know if Microsoft is planning to expand sql server Money
> > > data type to larger what it is in sql server 2000; that is larger than
> > > 922,337,203,685,477.5807?
> > >
> > > Thanks
> > >
> > > Hilal
> > >
> > >
> >
> >|||On Tue, 02 Dec 2003 23:49:37 +0100, Gert-Jan Strik
<sorry@.toomuchspamalready.nl> wrote:
>A bigger range for a money datatype is rediculous. Even the biggest
>budget of the biggest country will not exceed 900 trillion.
>I would suggest you simply handle any overflows. Who is going to spend
>900 trillion dollars in your shop by buying 10 million units that cost
>100 million dollars each? That just doesn't make sense.
Whilst in principle I agree with you, consider applications that must
handle foreign currencies. In an application I worked on recently for a
bank, I was somewhat surprised when a summary report returned figures in
the trillions. As it happened, it was due to my not converting foreign
currencies to local currency (AUD), but be aware that there are
situations where trillions of currency units are quite within realistic
bounds.
cheers,
Ross.
--
Ross McKay, WebAware Pty Ltd
"Words can only hurt if you try to read them. Don't play their game" - Zoolander
data type to larger what it is in sql server 2000; that is larger than
922,337,203,685,477.5807?
Thanks
HilalI haven't heard of such plans. You can always request at sqlwish@.microsoft.com. Or use NUMERIC
instead.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Hilal Issa" <hilal@.edm.com.lb> wrote in message news:u9ak8h9tDHA.2340@.TK2MSFTNGP12.phx.gbl...
> Does anyone know if Microsoft is planning to expand sql server Money
> data type to larger what it is in sql server 2000; that is larger than
> 922,337,203,685,477.5807?
> Thanks
> Hilal
>|||I don't know about future versions but if you want values larger than that
today use DECIMAL/NUMERIC which handles up to 38 digits preceision.
--
David Portas
--
Please reply only to the newsgroup
--
"Hilal Issa" <hilal@.edm.com.lb> wrote in message
news:u9ak8h9tDHA.2340@.TK2MSFTNGP12.phx.gbl...
> Does anyone know if Microsoft is planning to expand sql server Money
> data type to larger what it is in sql server 2000; that is larger than
> 922,337,203,685,477.5807?
> Thanks
> Hilal
>|||Thanks for the replies.
I will send an e-mail to sqlwish@.microsoft.com as Tibor suggested.
In fact, money data type would enough except in some cases where some values
might go beyond its boundaries; ex.: I have a table with 3 fields Qty, Unit
Amount and SubTotal (=Qty * Unit Amount). If we set Qty = 9999999 (seven
9's) and Unit Price = 99999999 (eight 9's)and Now calculate SubTotal = Qty *
Unit Amount, an overflow error is generated.
Indeed, I was trying converting all my fields using money datatype to
Decimal (38, 5) that is allowing 5 decimal places. I did not finish testing
with it yet. But I am guessing from now that I will have this problem with
wider range. Float (up to 1.79E + 308) would have been great but its
floating issue is not good at all in my case.
Best Regards
Hilal
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:SPidnZLuAOq5aleiRVn-hg@.giganews.com...
> I don't know about future versions but if you want values larger than that
> today use DECIMAL/NUMERIC which handles up to 38 digits preceision.
> --
> David Portas
> --
> Please reply only to the newsgroup
> --
> "Hilal Issa" <hilal@.edm.com.lb> wrote in message
> news:u9ak8h9tDHA.2340@.TK2MSFTNGP12.phx.gbl...
> > Does anyone know if Microsoft is planning to expand sql server Money
> > data type to larger what it is in sql server 2000; that is larger than
> > 922,337,203,685,477.5807?
> >
> > Thanks
> >
> > Hilal
> >
> >
>|||A bigger range for a money datatype is rediculous. Even the biggest
budget of the biggest country will not exceed 900 trillion.
I would suggest you simply handle any overflows. Who is going to spend
900 trillion dollars in your shop by buying 10 million units that cost
100 million dollars each? That just doesn't make sense.
My 5 cents,
Gert-Jan
Hilal Issa wrote:
> Thanks for the replies.
> I will send an e-mail to sqlwish@.microsoft.com as Tibor suggested.
> In fact, money data type would enough except in some cases where some values
> might go beyond its boundaries; ex.: I have a table with 3 fields Qty, Unit
> Amount and SubTotal (=Qty * Unit Amount). If we set Qty = 9999999 (seven
> 9's) and Unit Price = 99999999 (eight 9's)and Now calculate SubTotal = Qty *
> Unit Amount, an overflow error is generated.
> Indeed, I was trying converting all my fields using money datatype to
> Decimal (38, 5) that is allowing 5 decimal places. I did not finish testing
> with it yet. But I am guessing from now that I will have this problem with
> wider range. Float (up to 1.79E + 308) would have been great but its
> floating issue is not good at all in my case.
> Best Regards
> Hilal
> "David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
> news:SPidnZLuAOq5aleiRVn-hg@.giganews.com...
> > I don't know about future versions but if you want values larger than that
> > today use DECIMAL/NUMERIC which handles up to 38 digits preceision.
> >
> > --
> > David Portas
> > --
> > Please reply only to the newsgroup
> > --
> >
> > "Hilal Issa" <hilal@.edm.com.lb> wrote in message
> > news:u9ak8h9tDHA.2340@.TK2MSFTNGP12.phx.gbl...
> > > Does anyone know if Microsoft is planning to expand sql server Money
> > > data type to larger what it is in sql server 2000; that is larger than
> > > 922,337,203,685,477.5807?
> > >
> > > Thanks
> > >
> > > Hilal
> > >
> > >
> >
> >|||On Tue, 02 Dec 2003 23:49:37 +0100, Gert-Jan Strik
<sorry@.toomuchspamalready.nl> wrote:
>A bigger range for a money datatype is rediculous. Even the biggest
>budget of the biggest country will not exceed 900 trillion.
>I would suggest you simply handle any overflows. Who is going to spend
>900 trillion dollars in your shop by buying 10 million units that cost
>100 million dollars each? That just doesn't make sense.
Whilst in principle I agree with you, consider applications that must
handle foreign currencies. In an application I worked on recently for a
bank, I was somewhat surprised when a summary report returned figures in
the trillions. As it happened, it was due to my not converting foreign
currencies to local currency (AUD), but be aware that there are
situations where trillions of currency units are quite within realistic
bounds.
cheers,
Ross.
--
Ross McKay, WebAware Pty Ltd
"Words can only hurt if you try to read them. Don't play their game" - Zoolander
Subscribe to:
Posts (Atom)