Viewing 15 posts - 52,981 through 52,995 (of 59,091 total)
No... that's why the column number is "0". Read up on BCP Format Files... especially the example about skipping unwanted columns.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 9:19 pm
I'm with Steve... I use mixed case... it enforces capitalization and it's easier to hit the shift key than it is to hit the underscore when typing.
I agree with the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 9:16 pm
Raghavender (1/11/2008)
Thank you for your reply
You didn't answer the question... What is it that you want to do and why do you think you need to modify the system tables...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 9:13 pm
As a DBA, you shouldn't... there's not much that can't be done in T-SQL with the possible exception of RegEx (Regular expressions) and, despite what Books Online says about the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 9:09 pm
You CANNOT rely on the "% of Batch" listed in estimated or actual execution plans to determine which query is best... it can "lie" because it can't always see everything......
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 9:01 pm
Doesn't even need to be SSIS... can be some decent stored procs. But the point is an excellent one...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 8:36 pm
UDF's are typically RBAR...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 8:32 pm
Heh... It's amazing to me how many undocumented databases there are in the world. It also amazes me how many there are with no DRI... no DRI means no...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 8:29 pm
Step 1 should be to nomalize the table so things like this become much easier.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 8:17 pm
The real culprit is likely going to turn out to be a deadlock. You need to read "Deadlocks, detecting and ending" in Books Online. Pay particular attention to...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 8:03 pm
SQLElhassan (1/11/2008)
The Numbers table worked perfectly for me but I want to have my leading zero back in the PK field. Like I explained above, I'm...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 8:00 pm
aliciakw123 (1/10/2008)
I am trying to set up permissions in SQL 2005 to give a user Read Only rights to the table, but he needs to be able to create views.
As...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 7:55 pm
Would you please post the data in a code window so it doesn't wrap?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 7:51 pm
Exactly...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 7:48 pm
You should probably check which columns are in the index vs what you update in the tables... if you're modifying those columns, that'll certainly cause the index to jump about....
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 7:47 pm
Viewing 15 posts - 52,981 through 52,995 (of 59,091 total)