Can you redesign your Database tables? It has very bad relations and out put. Why you have 3 columns for Color1, Color2 and Color3 .With this Column how can you get your result .
Hello Jassim, while working in a procedure then i got the same problem. so based on my experience i would suggest to use decode function. decode function is similar to if else block.
decode(floor_id,null,1,floor_id)=decode(param_floor,null,1,param_floor)
thanks in advance regards, Sundeep
SQL Server will not do that. There are other tools associated with SQL Server that will. (Naturally this answer takes a vast leap as to what the question as such was.)
what you are not able to do, Truncate or addition of new data ? Whats the error ?
Mark the answer as accepted if that worked for you :). And for down-voters please specify the reason to improve the solution :).
It's an old DOS accounting program "Account Mate" using DBF files; Fox Pro; in which a Windows 7 and 8 application that I wrote for the customer provides extra features used all day long for electronic invoicing, electronic order confirmation, electronic past due statements via emails and PDF attachments. It's not exposed to the internet.
Yes I did, but there is no way I can cast decimal to float. I did a work around but it is ugly, it could cause a performance issue, so I am still looking for a better solution.
This could be intended :). With this a pointer to the first block in the data file that has a record with that value for its clustering field This seems reasonable
You are welcome! Richard's solution should have worked - that is the one I also tested and is exactly the approach I would have used. I only mentioned the cursor to help you understand the problem, but if it works ...! If Richard's query is performing badly, it could probably be improved with a well-chosen additional index. When you have some time, I'd suggest running it with the SQL query analyzer. Good luck!
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
It's a good idea, but we couldn't connect using SQL authentication either, which shouldn't involve AD at all.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
You're welcome, and thanks for posting the solution :) Might save someone else some days of frustration.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
Your SQL box timed out sending the mail to your mail server. You need to increase the timeout. Depending on which version of SQL you have, you might need to install a Cumulative Update in order to change the timeout: https://support.microsoft.com/kb/968834[^] You should then be able to use the sysmail_update_account_sp stored procedure[^] to increase the timeout.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Ibrahim.elh wrote:
what you proposed?
Create a small application, connect to the source-database, connect to the target-database, read a record from source, write a record to target.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
Two rows would be the expected result for a LEFT JOIN with that data. Each row from the table on the left will be returned once for each matching row in the table on the right, or once if there are no matching rows. Since the table on the right only has two rows, and the table on the left only has one row, the result will be two rows. Jeff Atwood has a good visual explanation of SQL joins: http://blog.codinghorror.com/a-visual-explanation-of-sql-joins/[^] Another way to explain joins:
Product the Cartesian Product of the two tables - each row in the left-hand table is matched with each row in the right-hand table.
Remove the rows where the JOIN condition is not met.
Depending on the JOIN type:
INNER JOIN: Nothing to do.
LEFT (OUTER) JOIN: Any rows in the left-hand table but not in the results are added back, matched with a row of NULL values for the right-hand table.
RIGHT (OUTER) JOIN:: Any rows in the right-hand table but not in the results are added back, matched with a row of NULL values for the left-hand table.
FULL (OUTER) JOIN: Apply the rules for both LEFT and RIGHT joins.
Filter the result based on the conditions in the WHERE clause (if any).
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
