Very similar.
If you are using SQL Server, you should be able look at the plan generated
in Query Analyser and I think you will find that Method 2/4 is more
efficient than 1.
Issues in SQL7 or 2000 setup? ... I am just trying to put a plan together to see what issues that I might see ... when setting up a new SQL server....RAM?...Prev by Date: ... (microsoft.public.sqlserver.setup)
Re: Slow UPDATE and DELETE on SQL Server 2000 ...databases: one on the new machine and one on the old machine (by the ... The plan from the old machine was more complex and has PARALLELISM ... > wrong with the SQL Server installation and unlikely that there are sub-system ... > linked-server driver parameters are not properly set. ... (microsoft.public.sqlserver.server)
Re: insert..select ...Parameter sniffing.... > The execution plan is vastly different. ... trigger on the target table. ... >> Tibor Karaszi, SQL Server MVP... (microsoft.public.sqlserver.server)
Re: Problem with Transaction backups ... You may need to drop and recreate the plan altogether if it doesn't save it by just editing it. ... Basically we have an SQL server that was running full backups and hourly ... a test database and tried the same thing and got the same results. ...Microsoft Analysis Services Client Tools 2005.090.3042.00 ... (microsoft.public.sqlserver.server)
Re: Reindex doesnt work ... The answer is that the whole affair with maintenance plan and reindexing ...SQL Server builds a query plan for the first time, ... passing a high-water mark as parameter. ... (microsoft.public.sqlserver.tools)
