Viewing 15 posts - 59,026 through 59,040 (of 59,067 total)
Worse than that, it's been my experience (in SQL Server 7) that a SELECT such as yours will create a separate instance of the view, in memory, for each named instance...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2004 at 7:02 am
Kokyan is correct... temp tables are always unique per session. You can see the actual name of a temp table in the tree view (press f8) of Query Analyzer. They...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2004 at 6:35 am
Actually, there is! It comes in the form of the PARSENAME command which was specifically developed to break apart the parts SQL object names "at the dots". Since your example...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2004 at 9:04 pm
Thought AH did a pretty good job! ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2004 at 9:20 pm
In that case, Bulk Insert has a MAX ERRORS setting that works just like the BCP -m parameter. Again, check BOL under Bulk Insert.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2004 at 9:06 pm
No execution plan is formed for Dynamic SQL until Runtime regardless of method of execution.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2004 at 5:53 am
Not sure but I think it may be the way that Crystal is using the view... I believe that it creates a different instance of the view for each instance that...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2004 at 7:34 pm
Kokyan gave a good example of "Dynamic SQL"... just wanted to remind everyone that dynamic SQL can be quite a bit slower than "Static SQL" because it does not pre-form...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2004 at 7:24 pm
It's a forum, not on-line help... ![]()
Anyway, use the -m parameter followed by the number of errors you wish to allow. Lookup BCP,Overview in...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2004 at 7:20 pm
1. You need to assign a "table alias" to the SELECT in the FROM clause.
2. You need to use that table alias on all column names to the right of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2004 at 5:03 pm
Basically, @@Error only lasts for one successful line of code so by the time you get to the "SET @out_param = @@Error" chunk of code, @@Error has been reset to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2004 at 4:56 pm
Add the "-n" parameter to your command line to suppress both the prompts and the line numbering.
Recommend you use OSQL instead.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2004 at 4:49 pm
Not sure if it uses the 'Sum of Product - Mod 10' method you were talking about but...
Have you tried the CHECKSUM function in SQL? It's in "Books on line".
--Jeff...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2004 at 4:34 pm
It's a bug and it's in BCP as well as bulk insert. The only time the "First Row" option works correctly is when the rows to be ignored, the first...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 20, 2004 at 6:21 am
The "-c" parameter, as you are probably aware, uses the CHAR format. What you might not know is that it adds the "newline" character as well. Hex "0D" is a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2004 at 10:56 pm
Viewing 15 posts - 59,026 through 59,040 (of 59,067 total)