Icarus

less info
stack exchange network profile network profile
169 reputation
6
bio website careers.stackoverflow.com/…
location
age 36
visits member for 1 year, 2 months
seen Jan 11 at 12:01
stats profile views 7

My Twitter account: @icarus

My Professional Profile.

My email: cmljYXJkb2phdmllcnNhbmNoZXpAZ21haWwuY29t - Come on, you should be able to recognize the encoding ;)

profile for Icarus on Stack Exchange, a network of free, community-driven Q&A sites


18 Actions

suggestions reviews revisions comments badges posts accepts all
Jan
10
 comment Efficient SQL database design for recording examples of a word
@Cory I agree and I thought of that and you are right, it's a dangerous design if not handled with care. I will remove the suggestion.
Jan
10
 answered Efficient SQL database design for recording examples of a word
Sep
21
 awarded  Custodian
Sep
17
 awarded  Scholar
Sep
17
 accepted Creating non-clustered Index on Partitioned Table that already has an existing Primary Key
Sep
14
 comment Creating non-clustered Index on Partitioned Table that already has an existing Primary Key
@SQLKiwi thanks for your comment. Yes, I am aware of this and it's a valid scenario for me.
Sep
14
 reviewed Approve suggested edit on Does dropping a Primary Key constraint from a Partitioned Table break the partition?
Sep
13
 asked Does dropping a Primary Key constraint from a Partitioned Table break the partition?
Sep
13
 awarded  Teacher
Sep
13
 revised Creating non-clustered Index on Partitioned Table that already has an existing Primary Key
deleted 10 characters in body
Sep
13
 awarded  Editor
Sep
13
 revised Creating non-clustered Index on Partitioned Table that already has an existing Primary Key
added 231 characters in body
Sep
13
 answered Creating non-clustered Index on Partitioned Table that already has an existing Primary Key
Sep
13
 comment Creating non-clustered Index on Partitioned Table that already has an existing Primary Key
@jnk I tried option A and the f***ing thing ran for over 4 hours to then throw the same Exception. Apparently Col_1 is a partitioned column in the table so I must make it part of every index I create, clustered or non-clustered. The problem for me is that this has been trial and error since I don't even have access to see table definitions in that environment. At least I think I have a better understanding of what's going on now. :\
Sep
12
 awarded  Student
Sep
12
 asked Creating non-clustered Index on Partitioned Table that already has an existing Primary Key
Jun
26
 awarded  Supporter
Mar
14
 answered Microsoft SQL server 2008 and linked servers