Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!
SQL Query multiplication
In SQL, I am updating a Table : PlacedOrderDetails by mutiplying two columns and entering the mutiplied values to the Qty Column.
[Ship Qty] which is nvarchar(255)
Mutiply with
[Size] which is nvarchar(255)
Resulted value goes to [Qty] which is float.
This is the Table value
Ship Qty Size Qty
2 100 EA 200
1 14.7 GM 14
Issue with my query is, decimal value of size column treated as round number and decimal part is ignored.
How to fix to treat whole number and decimal numbers equally?
[Ship Qty] which is nvarchar(255)
Mutiply with
[Size] which is nvarchar(255)
Resulted value goes to [Qty] which is float.
update PlacedOrderDetails
set Qty = [Ship Qty] * (cast(substring(Size, 1, patindex('%[^0-9]%', Size + '/') - 1) as float) * case when charindex('X', Size, 1) > 0 then
cast(substring(substring(Size, charindex('X', Size) + 1, len(Size)), 1, patindex('%[^0-9]%', substring(Size, charindex('X', Size) + 1, len(Size)) + '/') - 1) as float)
else 1 end )
WHERE Qty IS NULL
This is the Table value
Ship Qty Size Qty
2 100 EA 200
1 14.7 GM 14
Issue with my query is, decimal value of size column treated as round number and decimal part is ignored.
How to fix to treat whole number and decimal numbers equally?
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
For reasons you are experiencing now, it is a poor idea to include the numeric size (100) and unit of measure (EA) in the same field. Especially when you consider that a user can easily make a typo such that T-SQL can't uniformly split the numeric 14.7's from the char GM's.
Recommend you split these into two separate columns in your table.
Then the math would be easy.
Recommend you split these into two separate columns in your table.
Then the math would be easy.
Both @Jimhorn and @angelIII - I will not be able to modify existing Table which has thousands of records.
@Jimhorn, I can create a new table like temp_PlacedOrderdetails and create two different columns as Size and SizeUnit. But again, I need to take a lengthy permission as because database belongs to a Thirdparty software provider.
Anyways for me to fix it without changing the datatype or table schema
@Jimhorn, I can create a new table like temp_PlacedOrderdetails and create two different columns as Size and SizeUnit. But again, I need to take a lengthy permission as because database belongs to a Thirdparty software provider.
Anyways for me to fix it without changing the datatype or table schema
> I will not be able to modify existing Table which has thousands of records.
even if the table is containing records, you can modify the data types ...
you may add a new column with the proper data type, update that column from the existing one, drop the old column, and rename the new column
though you can work out your queries without changing data types, you will just end up with many more problems ...
"size" column should be 2 columns, one containing the "unit" type, the other the actual size value. ...
even if the table is containing records, you can modify the data types ...
you may add a new column with the proper data type, update that column from the existing one, drop the old column, and rename the new column
though you can work out your queries without changing data types, you will just end up with many more problems ...
"size" column should be 2 columns, one containing the "unit" type, the other the actual size value. ...
Table : PlacedOrderDetails , is loaded from a CSV file which has values SizeUnit (ie. 100 mg or 15 ml ) populated.
If i go with your decision, i have to create a new table such as temp_PlacedOrderDetails which export data from PlacedOrderDetails and split the value of Size Column to two different columns such as Size and Unit
If i go with your decision, i have to create a new table such as temp_PlacedOrderDetails which export data from PlacedOrderDetails and split the value of Size Column to two different columns such as Size and Unit
@ hpdvs2
Where should i implement your regex expression.
Because, i haven't seen $ sign on my query ???
Where should i implement your regex expression.
Because, i haven't seen $ sign on my query ???
regex format is not working , it throws error saying Substring conversion error !!
I am sure, we can achieve this through Patindex and Charindex. But having problem on formating the decimal.
Something like i am expecting
Case when ( if size column is decimal ) do this
else do this
I am sure, we can achieve this through Patindex and Charindex. But having problem on formating the decimal.
Something like i am expecting
Case when ( if size column is decimal ) do this
else do this
I believe it supposed to be this, but I don't use regex a lot. The key is that you get the decimal place as well.
One of those two should work. Otherwise just search for
patindex('^(([0-9]*)|(([0-9]*).([0-9]*)))$'
patindex('/^\d+\.?\d*$/'
One of those two should work. Otherwise just search for
regex get numeric with decimal
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial
Thank you, I am searching online for the Patindex format. But as per your suggestion, i am getting errors ..
Error :
Invalid length parameter passed to the LEFT or SUBSTRING function.
The statement has been terminated.
update PlacedOrderDetails
set Qty = [Ship Qty] * (cast(substring(Size, 1, patindex('^(([0-9]*)|(([0-9]*).([0-9]*)))$', Size + '/') - 1) as float) * case when charindex('X', Size, 1) > 0 then
cast(substring(substring(Size, charindex('X', Size) + 1, len(Size)), 1, patindex('^(([0-9]*)|(([0-9]*).([0-9]*)))$', substring(Size, charindex('X', Size) + 1, len(Size)) + '/') - 1) as float)
else 1 end )
WHERE Qty IS NULL
Error :
Invalid length parameter passed to the LEFT or SUBSTRING function.
The statement has been terminated.
I changed the regex from '%[^0-9]%' to '%[A-Z]%'
Issue is fixed. An expert @Jared_s solved the issue in this posting :
http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/Q_27978053.html
Issue is fixed. An expert @Jared_s solved the issue in this posting :
http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/Q_27978053.html
update PlacedOrderDetails
set Qty = [Ship Qty] * (cast(substring(Size, 1, patindex('%[A-Z]%', Size + '/') - 1) as float) * case when charindex('X', Size, 1) > 0 then
cast(substring(substring(Size, charindex('X', Size) + 1, len(Size)), 1, patindex('%[A-Z]%', substring(Size, charindex('X', Size) + 1, len(Size)) + '/') - 1) as float)
else 1 end )
WHERE Qty IS NULL
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
^(([0-9]*)|(([0-9]*).([0-9