June 26, 2008 at 2:11 am
I found that nothing wrong with the dump ,the issue is with SQL server Result set as it can display only upto some extend....What can i do to view the entire data in SQL Server Result set???:w00t:
June 27, 2008 at 2:44 am
In SSMS, select the Tools menu, then Options. Expand Query Results then set the values to what you need. There will always be a maximum size that can be displayed in SSMS, as your box will not have enough memory to display the maximum possible size of LOB columns.
Even when you have made these changes, SSMS will limit the width of the display column. If you think the data is wider than the amount displayed, put the cursor on the virtical divider to the right of the column header. You can then drag this to the right to make the display column wider, or you can double-click on it to set the width to the size needed to show all data on the page currently being displayed. Note that if the next page has wider data, then you may need to increase the width of the display column again when you display the next page.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
June 27, 2008 at 7:26 am
Maybe you can use this:
dbcc checkdb (yourdb) WITH ALL_ERRORMSGS, DATA_PURITY
BOL says
DATA_PURITY
Causes DBCC CHECKDB to check the database for column values that are not valid or out-of-range. For example, DBCC CHECKDB detects columns with date and time values that are larger than or less than the acceptable range for the datetime data type; or decimal or approximate-numeric data type columns with scale or precision values that are not valid.
For databases created in SQL Server 2005, column-value integrity checks are enabled by default and do not require the DATA_PURITY option. For databases upgraded from earlier versions of SQL Server, column-value checks are not enabled by default until DBCC CHECKDB WITH DATA_PURITY has been run error free on the database. After this, DBCC CHECKDB checks column-value integrity by default. For more information about how CHECKDB might be affected by upgrading database from earlier versions of SQL Server, see the Remarks section later in this topic.
If PHYSICAL_ONLY is specified, column-integrity checks are not performed.
Validation errors reported by this option cannot be fixed by using DBCC repair options. For information about manually correcting these errors, see Knowledge Base article 923247: Troubleshooting DBCC error 2570 in SQL Server 2005.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply