Viewing 15 posts - 51,361 through 51,375 (of 59,091 total)
Marios Philippopoulos (4/1/2008)
Matt Miller (4/1/2008)
Which is an interesting thought. The problem is - I'm pretty sure you have to flag that CLR as "unsafe" in order for it to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 10:58 am
I agree... he must be busy on Simple-Talk. We should pay him a visit. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 10:53 am
Nicely done John... You saying you like Scenario 1 or something? 😉
You should see how fast things run in the NV tables when you've had the time to add the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 10:52 am
Andre T (4/1/2008)
Your right Gail, I have nothing to loose by feedback from people who know more than I(except some or even lots humiliation - HA!).
No, no... no humiliation......
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 10:46 am
p.s. The steps you take to get the raw data file from wherever should also be included. Of course, no username/passwords, please.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 10:26 am
Lowell (4/1/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 10:25 am
Matt Miller (4/1/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 10:20 am
Marios Philippopoulos (4/1/2008)
Ask how many DBA's allow developers to have write privs to production.
It's not about DBAs allowing devs direct access to production. It has nothing to do with that.
It's...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 10:12 am
GilaMonster (4/1/2008)
Andre T (3/31/2008)
The big picture is a bit complicated. I certainly realize set based is better but...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 9:46 am
Marios Philippopoulos (4/1/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 9:43 am
Lowell (4/1/2008)
The data I'm trying to parse is some FIP55 data with every place name in the united states; 560 meg of data,...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 9:30 am
Spot on Antonio... real key is that the data should never have come into the database in an unsplit fashion to begin with. They should use Bulk Insert or...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 9:28 am
Loner (4/1/2008)
"Though shalt have no greater database authority than the DBA."
What if the DBA does not know anything except backup and restore database? I have seen a lot of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 8:02 am
Heh... I can see why... There is a bit of "religion" there...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 7:11 am
No need...
SELECT Table_Name, Column_Name FROM Information_Schema.Columns
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 7:01 am
Viewing 15 posts - 51,361 through 51,375 (of 59,091 total)