Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook



The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic

Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.

If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.

Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.

Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

MS SQL 2012 Max Row Size in Bytes

  • Filter
  • Time
  • Show
Clear All
new posts

  • richard2007
    Re: MS SQL 2012 Max Row Size in Bytes

    So i took the advice given in this post and split the table. This turned out to be a very worthwhile excercise. Features added to the app over the last 10 years caused the app to become bloated and i also identified better ways to do things. Splitting the tables has allowed me to re think how we do things and i have been able to streamline the tables and our processes.

    I have been using nvarchar(MAX) for the large data fields.

    thanks again everyone.

    Leave a comment:

  • ids-dave
    Re: MS SQL 2012 Max Row Size in Bytes

    For your large text fields, I recommend you define the SQL data type as "nvarchar(MAX)". SQL will make better use of the storage used at the record level based on the amount of data entered into these fields. In your grid/UX, set the properties - control type to textarea which opens up additional choices for defining how the field will be presented to the user. Fields defined this way can be searched just like a text field.

    Leave a comment:

  • -Jinx-
    Re: MS SQL 2012 Max Row Size in Bytes

    Hi Richard,

    I think what Steve and Pat are saying is that actually querying for that row will take more time based on the sizes of the columns in the query. Rendering it in HTML will take more time as well (so you might want that in a clickable detail view of some sort) but that's a front-end concern. As far as working with the back-end, their advice is golden, namely breaking up your table into multiple smaller ones and using joins only when needed. For instance, you could have one table containing only the 30 fields with the walls of text in them and link them with a unique identifier to your other table.

    For just one example on how you might do it, you could put all 30 of those columns into one column and have a unique id column along side it along with a foreign key unique id from your main table, so 3 columns. Your main table then would only carry the unique id of the wall of text from your "wallOText" table in all 30 of those text columns. This will make all operations on your main table way faster. If you need to search the walls of text, simply join them in when needed using the unique id's to do so (wallOText.UniqueID = MainTable.textField1) etc.

    As Pat says, you can also break up your tables further and group them into ways that make sense as far as how your using the application. Lastly, some of my own .02, you can create views based on common sections of tables and joins of them to use for search purposes.

    As Pat says, do it now, you won't regret it, you (or someone else) will just end up doing it later anyway.
    Last edited by -Jinx-; 03-22-2017, 03:48 PM.

    Leave a comment:

  • richard2007
    Re: MS SQL 2012 Max Row Size in Bytes

    that's really helpful, thank you.

    i will only ever get one row of data at a time and the forms will only display a small number of the columns at any one time so the queries should be small. i'll try one table first with some test data and see how that goes.

    Leave a comment:

  • Pat Bremkamp
    Re: MS SQL 2012 Max Row Size in Bytes

    If I remember correctly, the limit is 65,000 and change characters, so less bytes if you have double byte characters. But, I have a table with about 150 fields and I hate it every day. It works, but I am constantly scrolling back and forth to check something and it is painful. So, after 4 years of collecting data, with millions of rows, I'm starting to break that up into 5 different tables and joining them if I need data for more than one row. Take Steve's advice and do it now!

    There are two different ways to break it up. If you expect a large number of rows, you can put your text fields in one table (especially if you will be doing full text searches) and all the fixed length fields in another. The fixed length tables are much faster to search.

    The other way is to group them to minimize the number of joins by putting all the fields you expect to need in one form in one table.

    Or, like me, a combination of those.

    Leave a comment:

  • Steve Workings
    Re: MS SQL 2012 Max Row Size in Bytes

    You should be fine. Maybe go ahead and create the table, fill a row with test data (Lorem Ipsum...) and make sure.

    Tables with rows this large do affect performance a little -- it takes a bit longer to collect all that data (even from one row) and get it to the client, and data rendered.


    1. If you can break the table into smaller logical pieces, this is a good time to consider that.
    2. Make sure your queries don't select * from the table -- just what you need
    3. Make sure your queries select only the records you need each time.

    Leave a comment:

  • richard2007
    started a topic MS SQL 2012 Max Row Size in Bytes

    MS SQL 2012 Max Row Size in Bytes

    in my quest to convert to MS SQL, which is going prety well so far, i am now at the stage of building the components for one of tables imported from .dbf.

    This table has a lot of fields for the user to enter text of about 500 characters or even more. i think there are about 30 fields like this plus another 100 fields of other data types such as dates, bigint and bytes.

    i have read that there is a maximum byte count per row in the table and i feel this will exceed it. so i just wanted to get opinions as to whether i am going to run in to trouble? do i need to split the table? or will i be ok?