Viewing 15 posts - 51,376 through 51,390 (of 59,102 total)
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
Start here...
http://www.sqlservercentral.com/articles/Test+Data/61572/
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 6:59 am
Heh... Never got around to finishing those... can't find any developers that can follow the first commandment...
"Though shalt have no greater database authority than the DBA."
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 6:56 am
So, you're saying that a DBA must learn all possible languages that may be compiled into a CLR and have the ability to review the source code from same? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 6:40 am
No, no... that's one of the 10 Commandments of Developers...
"Thou shalt not commit RBAR" 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 6:25 am
Viewing 15 posts - 51,376 through 51,390 (of 59,102 total)