Viewing 15 posts - 47,716 through 47,730 (of 59,099 total)
Matt Miller (10/15/2008)
Jeff - enquiring minds wanna know - how are you getting your code windows to scroll side to side?
I think Steve's in-house Ninja tweeked the forum code for...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2008 at 10:28 pm
Here's a working example of the BCP/XP_CmdShell method. If you don't need a header, just comment it out...
--===== These could be parameters in a stored procedure
DECLARE @Directory ...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2008 at 10:19 pm
heh... you forgot the last step, Seth...
* pensively turns beer into lager *
🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2008 at 10:08 pm
Thanks, Eric. The only thing I'd worry about now is the performance hit of using both a table valued function and a cross-apply to drive it home. If...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2008 at 10:02 pm
Sorry... the day's coffee is wearing off. 🙂 I didn't read all of your last...
You're correct. Since the rows are going to be added on a onesy basis,...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2008 at 9:58 pm
Matt Miller (10/15/2008)
Jeff Moden (10/15/2008)
In that case, I'd use a FILL Factor of 100 for that tiny bit more speed on any SELECTS you may do on the table.
True -...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2008 at 9:48 pm
rbarryyoung (10/15/2008)
So that's in-between LGD and Cryptographic? And I don't see any varbinary(MAX) or sql_variant data-types. 😀
Heh... no... It's somewhere in between a pork chop and a chicken...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2008 at 9:46 pm
In that case, I'd use a FILL Factor of 100 for that tiny bit more speed on any SELECTS you may do on the table.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2008 at 7:20 pm
Garadin (10/15/2008)
This solution is a variation of Jeff Moden's Running Total Technique, which can be found here:http://www.sqlservercentral.com/articles/Advanced+Querying/61716/
Thanks for the "pass back", Seth. After Matt's index suggestion, looks like you've...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2008 at 7:15 pm
David O (10/15/2008)
Once you get your formatting issues fixed the function is datediff. Check out Books on line for the details of the function.
Actually, once converted, you can just...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2008 at 7:02 pm
According to the following...
http://msdn.microsoft.com/en-us/library/aa258866(SQL.80).aspx
... the Test returned is of the data type TEXT which can contain up to 2 billion characters. But, the largest "column width" you can set...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2008 at 6:58 pm
Marianne,
Actually, I'd be very interested in the performance of the queries. Could you tell us how many rows ended up in the table and how many of them had...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2008 at 6:49 pm
eric (10/15/2008)
Nevermind.....I found my mistake....after 3 hours. I tried to delete the post but it's not working !
Would you mind telling us what your mistake was? Might save...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2008 at 6:16 pm
sudrav (10/15/2008)
1. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2008 at 6:15 pm
The way you deal with different coding styles is by insisting that there only be one coding style. Publish and enforce a set of standards including such arcane things...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2008 at 6:08 pm
Viewing 15 posts - 47,716 through 47,730 (of 59,099 total)