July 14, 2015 at 9:12 am
WayneS (7/14/2015)
Brandie Tarvin (7/14/2015)
Steve Jones - SSC Editor (7/13/2015)
Brandie Tarvin (7/11/2015)
Kind of irked this morning. Found out this morning that the SQL Saturday call for speakers in Orlando closed after only a week.Usually the call for speakers is open for a lot longer than that, and I had month end and server install stuff to do, so I hadn't gotten around to submitting my sessions yet.
Oh, well. I guess I'm not submitting at all.
Hmm, what email? Orlando has been open for awhile. Been on my list.
I got a call for speakers on Friday July 3rd and then the email reminder that the speakers call was closing on July 10th.
I received the original call for speakers for Orlando on 4/29.
Really? Hrm. I will go back and check.
July 14, 2015 at 9:16 am
WayneS (7/14/2015)
Lynn Pettis (7/14/2015)
I know that an OP posted a question with the following error:Cannot create a row of size 8071 which is greater than the allowable maximum row size of 8060. The statement has been terminated.
There was a suggestion offered that helped them and it wasn't rebuilding the clustered index. I can't seem to find the thread and we are getting this error in HOA (Horn of Africa, not Home Owners Association).
Is the database in the Snapshot transaction isolation level?
No, nothing that esoteric. Just your out of the box Read Committed using Simple Recovery model. I suggested they rebuild the clustered index (had a similar issue while I was in Afghanistan and that fixed that issue during an upgrade), but the thread I am looking for they ended up doing something different and cleared it as well. I can't even remember who the OP was for the issue.
July 14, 2015 at 9:19 am
Brandie Tarvin (7/14/2015)
Lynn Pettis (7/14/2015)
I know that an OP posted a question with the following error:Cannot create a row of size 8071 which is greater than the allowable maximum row size of 8060. The statement has been terminated.
There was a suggestion offered that helped them and it wasn't rebuilding the clustered index. I can't seem to find the thread and we are getting this error in HOA (Horn of Africa, not Home Owners Association).
Is this the thread?
Nope. The thread I am looking for, iirc, had the OP trying to change the data type of one of the columns.
July 14, 2015 at 9:35 am
Lynn Pettis (7/14/2015)
I know that an OP posted a question with the following error:Cannot create a row of size 8071 which is greater than the allowable maximum row size of 8060. The statement has been terminated.
There was a suggestion offered that helped them and it wasn't rebuilding the clustered index. I can't seem to find the thread and we are getting this error in HOA (Horn of Africa, not Home Owners Association).
I guess you are referring to this thread
😎
July 14, 2015 at 10:06 am
WayneS (7/14/2015)
Jeff Moden (7/14/2015)
Lynn Pettis (7/13/2015)
OMG! How does Silver Spoon keep his job? Member of ssc for over 10 years and can't seem to do the simplest tasks without running to the internet.What's the link for this thread, Lynn?
http://www.sqlservercentral.com/Forums/Topic1702273-3077-1.aspx
Oh that one! Some things are better left unsaid!
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
July 14, 2015 at 10:34 am
You know, I wondered about Silver Spoon in the past. Why (s)he was asking certain questions when I thought (s)he had more info at her/his fingertips. But I never noticed the pattern.
Now that you point it out... I'm going to have to rethink all my future responses.
July 14, 2015 at 11:14 am
Eirikur Eiriksson (7/14/2015)
Lynn Pettis (7/14/2015)
I know that an OP posted a question with the following error:Cannot create a row of size 8071 which is greater than the allowable maximum row size of 8060. The statement has been terminated.
There was a suggestion offered that helped them and it wasn't rebuilding the clustered index. I can't seem to find the thread and we are getting this error in HOA (Horn of Africa, not Home Owners Association).
I guess you are referring to this thread
😎
Yes, thank you. I even responded on that thread and still couldn't find it.
July 14, 2015 at 11:20 am
Lynn Pettis (7/14/2015)
Eirikur Eiriksson (7/14/2015)
Lynn Pettis (7/14/2015)
I know that an OP posted a question with the following error:Cannot create a row of size 8071 which is greater than the allowable maximum row size of 8060. The statement has been terminated.
There was a suggestion offered that helped them and it wasn't rebuilding the clustered index. I can't seem to find the thread and we are getting this error in HOA (Horn of Africa, not Home Owners Association).
I guess you are referring to this thread
😎
Yes, thank you. I even responded on that thread and still couldn't find it.
Wow. That's an interesting read. Now I want to go in and test creating a huge table.
I also wonder how many tables in our databases are afflicted with this issue given all the changes we've made over the years.
EDIT: "This issue" meaning how many tables could be cleaned and bring down the size of our dbs, not how many tables have this error.
July 14, 2015 at 11:26 am
Lynn Pettis (7/14/2015)
Eirikur Eiriksson (7/14/2015)
Lynn Pettis (7/14/2015)
I know that an OP posted a question with the following error:Cannot create a row of size 8071 which is greater than the allowable maximum row size of 8060. The statement has been terminated.
There was a suggestion offered that helped them and it wasn't rebuilding the clustered index. I can't seem to find the thread and we are getting this error in HOA (Horn of Africa, not Home Owners Association).
I guess you are referring to this thread
😎
Yes, thank you. I even responded on that thread and still couldn't find it.
I did remember the 8061, easy to find it searching for that. Had a similar problem at the time and was also helping the OP with another problem.
😎
July 14, 2015 at 11:31 am
July 14, 2015 at 11:37 am
July 14, 2015 at 11:44 am
Brandie Tarvin (7/14/2015)
Lynn Pettis (7/14/2015)
Eirikur Eiriksson (7/14/2015)
Lynn Pettis (7/14/2015)
I know that an OP posted a question with the following error:Cannot create a row of size 8071 which is greater than the allowable maximum row size of 8060. The statement has been terminated.
There was a suggestion offered that helped them and it wasn't rebuilding the clustered index. I can't seem to find the thread and we are getting this error in HOA (Horn of Africa, not Home Owners Association).
I guess you are referring to this thread
😎
Yes, thank you. I even responded on that thread and still couldn't find it.
Wow. That's an interesting read. Now I want to go in and test creating a huge table.
I also wonder how many tables in our databases are afflicted with this issue given all the changes we've made over the years.
EDIT: "This issue" meaning how many tables could be cleaned and bring down the size of our dbs, not how many tables have this error.
Look up Housekeeping in "the manual", chapter "Elephant in your database":-P
😎
BTW Survey data is more like a herd of Elephants, had my share of that in the past.
July 14, 2015 at 11:50 am
Eirikur Eiriksson (7/14/2015)
Brandie Tarvin (7/14/2015)
Lynn Pettis (7/14/2015)
Eirikur Eiriksson (7/14/2015)
Lynn Pettis (7/14/2015)
I know that an OP posted a question with the following error:Cannot create a row of size 8071 which is greater than the allowable maximum row size of 8060. The statement has been terminated.
There was a suggestion offered that helped them and it wasn't rebuilding the clustered index. I can't seem to find the thread and we are getting this error in HOA (Horn of Africa, not Home Owners Association).
I guess you are referring to this thread
😎
Yes, thank you. I even responded on that thread and still couldn't find it.
Wow. That's an interesting read. Now I want to go in and test creating a huge table.
I also wonder how many tables in our databases are afflicted with this issue given all the changes we've made over the years.
EDIT: "This issue" meaning how many tables could be cleaned and bring down the size of our dbs, not how many tables have this error.
Look up Housekeeping in "the manual", chapter "Elephant in your database":-P
😎
BTW Survey data is more like a herd of Elephants, had my share of that in the past.
So I'm testing a quick bit of code on a dev version of our bigger reporting database and it found something on the first table it hit. Nothing else so far, though. I'm doing it automagically with dynamic sql and INFORMATION_SCHEMA.TABLES.
That was definitely a fun exercise in trying to write code without using my usual DoneNotDone bit column in a temp table referenced by my loop. Adding to personal knowledge store = DBA Success. YAY!
July 14, 2015 at 12:02 pm
Brandie Tarvin (7/14/2015)
Eirikur Eiriksson (7/14/2015)
Brandie Tarvin (7/14/2015)
Lynn Pettis (7/14/2015)
Eirikur Eiriksson (7/14/2015)
Lynn Pettis (7/14/2015)
I know that an OP posted a question with the following error:Cannot create a row of size 8071 which is greater than the allowable maximum row size of 8060. The statement has been terminated.
There was a suggestion offered that helped them and it wasn't rebuilding the clustered index. I can't seem to find the thread and we are getting this error in HOA (Horn of Africa, not Home Owners Association).
I guess you are referring to this thread
😎
Yes, thank you. I even responded on that thread and still couldn't find it.
Wow. That's an interesting read. Now I want to go in and test creating a huge table.
I also wonder how many tables in our databases are afflicted with this issue given all the changes we've made over the years.
EDIT: "This issue" meaning how many tables could be cleaned and bring down the size of our dbs, not how many tables have this error.
Look up Housekeeping in "the manual", chapter "Elephant in your database":-P
😎
BTW Survey data is more like a herd of Elephants, had my share of that in the past.
So I'm testing a quick bit of code on a dev version of our bigger reporting database and it found something on the first table it hit. Nothing else so far, though. I'm doing it automagically with dynamic sql and INFORMATION_SCHEMA.TABLES.
That was definitely a fun exercise in trying to write code without using my usual DoneNotDone bit column in a temp table referenced by my loop. Adding to personal knowledge store = DBA Success. YAY!
I never use the INFORMATION_SCHEMA views personally preferring to use the system views like sys.tables, sys.columns, etc.
I've written quite a bit of dynamic SQL in my current position.
July 14, 2015 at 12:20 pm
Brandie Tarvin (7/14/2015)
So I'm testing a quick bit of code on a dev version of our bigger reporting database and it found something on the first table it hit. Nothing else so far, though. I'm doing it automagically with dynamic sql and INFORMATION_SCHEMA.TABLES.That was definitely a fun exercise in trying to write code without using my usual DoneNotDone bit column in a temp table referenced by my loop. Adding to personal knowledge store = DBA Success. YAY!
Suggest you stop using the INFORMATION_SCHEMA views, the old ANSI standard objects are there for backward compatibility, nothing else. Even MS advices against it
😎
Viewing 15 posts - 49,471 through 49,485 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply