Comments
Sort by recent activity
intGod said:
Best practice to only use a TABLE ALIAS in the UPDATE statement so you will always have to have it explicitly in the FROM statement
Thanks for your advice. But as you know SQL Prompt is prode of his advices and detecting potencial programers mistakes. Here we have a case that worth for seriouse warning to the programer. I am wondernig why Microsoft has not covered the issue. As you surely have noticed if you run an UPDATE command without WHERE clause, SSMS shows a warning before runing it. My issue is similar to that condition, UPDATE all records without any warnings. / comments
intGod said:
Best practice to only use a TABLE ALIAS in the UPDATE statement so you will always have to have it explicitly in the FROM statement
Thanks for your advice.But as you know SQL Pr...
Dan_J said:
Hi @Omid,
Thanks for reaching out to us regarding this and for bring this to our attention.
I'd
like to try and replicate the issue you are seeing to better understand
the issue and then potentially escalate it to our development team.
Would it be possible to get a copy of your syntax around the following?:
WITH Tree AS ( here I make a tree, without problem ) UPDATE dbo.whs_Inventory SET ProfileId = NULL FROM Tree WHERE Tree.ParentId IS NOT NULL
Hi Thanks for your comment my complete code was: <div>WITH Tree AS </div><div> ( SELECT inv.InventoryId, inv.ParentId, inv.ProfileId </div><div> FROM dbo.whs_Inventory inv INNER JOIN </div><div> dbo.whs_ReceiptDetail RD ON RD.QRcode = inv.QRcode INNER JOIN</div><div> Inserted ins ON ins.ReceiptMasterId = RD.ReceiptMasterId INNER JOIN </div><div> Deleted del ON del.ReceiptMasterId = ins.ReceiptMasterId</div><div> WHERE ins.ReceiptConfirm =1 AND del.ReceiptConfirm=0</div><div> UNION ALL</div><div> SELECT child.InventoryId , child.ParentId, child.ProfileId <br></div><div> FROM dbo.whs_Inventory child INNER JOIN
Tree ON child.ParentId = Tree.InventoryId</div><div>)</div><div>UPDATE dbo.whs_Inventory</div><div>SET ProfileId = NULL,</div><div> DeliveryDate = NULL</div><div>FROM Tree </div><div>WHERE ParentId IS NOT NULL
/* -- Correct From cluase is :
<pre class="CodeBlock"><code><div>FROM dbo.whs_Inventory inv INNER JOIN <br></div><div> Tree ON Tree.InventoryId = inv.InventoryId</div><div>WHERE Tree.ParentId IS NOT NULL</div>
*/
/ comments
Dan_J said:
Hi @Omid,
Thanks for reaching out to us regarding this and for bring this to our attention.
I'd
like to try and replicate the issue you are seeing to better understand
the iss...
I want to add my previous post that I un-installed all red-gate products, then installed SQLSearch_3.5.0.2590.exe that I found its link in this forum. It started to work without any problem. but as soon as I installed SQL prompt (last version is unfortuanted wraped in a big boundle : SQLToolbelt.exe), the problem again started. I had just selected SQL prompt while installation because SQL search was installed already. But this did not help. Thanks every body / comments
I want to add my previous post that I un-installed all red-gate products, then installed SQLSearch_3.5.0.2590.exe that I found its link in this forum.It started to work without any problem.but as s...
I have the same problem. I guess the ToolBelt installer is copying some new VC++ dlls or something that cause the problem. Even after uninstalling or downgrade to SQL prompt v9.0 did not help / comments
I have the same problem. I guess the ToolBelt installer is copying some new VC++ dlls or something that cause the problem. Even after uninstalling or downgrade to SQL prompt v9.0 did not help
I had the same experience when I upgraded my SSMS and SQL search to the latest version the problem started. Even after rolling back to previous versions did not solve my problem. I think I have to install a clean new Win 10 an re-install every thing. Refreshing Object explorer does not do any thing for me. I search som text that some triggers and functions appear in result , and double click on them or right click menu just opens the Object Explorer but does not locate the procedure / comments
I had the same experience when I upgraded my SSMS and SQL search to the latest version the problem started. Even after rolling back to previous versions did not solve my problem.I think I have to i...