SQL Server Management Studio Results Scrolling
I find myself doing a lot of scrolling through thru hundreds of results within the SSMS which is pretty painful. Does anyone know a faster way to scroll through a large number of Results in SSMS? Page down doesn't seem to be supported. Even if there was an option to go to a specific row within the results would be a big help.
ssms
asked Nov 24 '18 at 19:39
wilbevwilbev
1,46641826
add a comment |
I find myself doing a lot of scrolling through thru hundreds of results within the SSMS which is pretty painful. Does anyone know a faster way to scroll through a large number of Results in SSMS? Page down doesn't seem to be supported. Even if there was an option to go to a specific row within the results would be a big help.
ssms
asked Nov 24 '18 at 19:39
wilbevwilbev
1,46641826
2
Can you please define "large number of results" ? millions? a couple of millions? If that is the case, SSMS may not be the right way of viewing such number of records
– Ozan Gunceler
Jan 4 at 7:43
1
I agree with @OzanGunceler: If you're scrolling through a large amount of results in SSMS, trying to find a specific row, I think you'd be better off revising your query (as in his answer). You can also save your results to a CSV file, and then open it up in Excel.
– Zack
Jan 4 at 14:36
This is typically less than 50K records. Definitely agree on changing the query however, in this case it's an debug/error log so for troubleshooting reasons you need to see the records as they are recorded.
– wilbev
Jan 5 at 22:06
add a comment |
I find myself doing a lot of scrolling through thru hundreds of results within the SSMS which is pretty painful. Does anyone know a faster way to scroll through a large number of Results in SSMS? Page down doesn't seem to be supported. Even if there was an option to go to a specific row within the results would be a big help.
ssms
asked Nov 24 '18 at 19:39
wilbevwilbev
1,46641826
I find myself doing a lot of scrolling through thru hundreds of results within the SSMS which is pretty painful. Does anyone know a faster way to scroll through a large number of Results in SSMS? Page down doesn't seem to be supported. Even if there was an option to go to a specific row within the results would be a big help.
ssms
ssms
asked Nov 24 '18 at 19:39
wilbevwilbev
1,46641826
asked Nov 24 '18 at 19:39
wilbevwilbev
1,46641826
asked Nov 24 '18 at 19:39
wilbevwilbev
1,46641826
asked Nov 24 '18 at 19:39
wilbevwilbev
1,46641826
asked Nov 24 '18 at 19:39
wilbevwilbev
1,46641826
1,46641826
2
Can you please define "large number of results" ? millions? a couple of millions? If that is the case, SSMS may not be the right way of viewing such number of records
– Ozan Gunceler
Jan 4 at 7:43
1
I agree with @OzanGunceler: If you're scrolling through a large amount of results in SSMS, trying to find a specific row, I think you'd be better off revising your query (as in his answer). You can also save your results to a CSV file, and then open it up in Excel.
– Zack
Jan 4 at 14:36
This is typically less than 50K records. Definitely agree on changing the query however, in this case it's an debug/error log so for troubleshooting reasons you need to see the records as they are recorded.
– wilbev
Jan 5 at 22:06
add a comment |
2
Can you please define "large number of results" ? millions? a couple of millions? If that is the case, SSMS may not be the right way of viewing such number of records
– Ozan Gunceler
Jan 4 at 7:43
1
I agree with @OzanGunceler: If you're scrolling through a large amount of results in SSMS, trying to find a specific row, I think you'd be better off revising your query (as in his answer). You can also save your results to a CSV file, and then open it up in Excel.
– Zack
Jan 4 at 14:36
This is typically less than 50K records. Definitely agree on changing the query however, in this case it's an debug/error log so for troubleshooting reasons you need to see the records as they are recorded.
– wilbev
Jan 5 at 22:06
2
2
Can you please define "large number of results" ? millions? a couple of millions? If that is the case, SSMS may not be the right way of viewing such number of records
– Ozan Gunceler
Jan 4 at 7:43
Can you please define "large number of results" ? millions? a couple of millions? If that is the case, SSMS may not be the right way of viewing such number of records
– Ozan Gunceler
Jan 4 at 7:43
1
1
I agree with @OzanGunceler: If you're scrolling through a large amount of results in SSMS, trying to find a specific row, I think you'd be better off revising your query (as in his answer). You can also save your results to a CSV file, and then open it up in Excel.
– Zack
Jan 4 at 14:36
I agree with @OzanGunceler: If you're scrolling through a large amount of results in SSMS, trying to find a specific row, I think you'd be better off revising your query (as in his answer). You can also save your results to a CSV file, and then open it up in Excel.
– Zack
Jan 4 at 14:36
This is typically less than 50K records. Definitely agree on changing the query however, in this case it's an debug/error log so for troubleshooting reasons you need to see the records as they are recorded.
– wilbev
Jan 5 at 22:06
This is typically less than 50K records. Definitely agree on changing the query however, in this case it's an debug/error log so for troubleshooting reasons you need to see the records as they are recorded.
– wilbev
Jan 5 at 22:06
add a comment |
2 Answers
2
active
oldest
votes
Not directly achievable through SSMS interface but you can try something like the following.
First, determine which row number you'd like to jump to (index starts at one) and execute your query with the OFFSET and FETCH NEXT statements
SELECT * FROM Expense ORDER BY Id ASC OFFSET 4 ROWS FETCH NEXT 1 ROWS ONLY
OFFSET means how many rows you'd like to skip from the top, FETCH NEXT determines how many rows to display after the offset.
You can select the first row after skipping 20 rows (in other words, obtaining row 21), do the following
SELECT * FROM Expense ORDER BY Id ASC OFFSET 20 ROWS FETCH NEXT 1 ROWS ONLY
Not the best way of doing it, did not consider performance of such approach. But the easiest to achieve what you are looking for.
Another way could be executing the full query in Excel and use Ctrl + G to go to specific row number.
answered Jan 4 at 14:05
Ozan GuncelerOzan Gunceler
848510
add a comment |
There is no direct option for easy scrolling. You need to filter the result or export/copy the result to excel.
Usually I will copy the result to excel. This will give a clean look and also we can filter the result if needed in excel. :)
answered Jan 4 at 18:44
BinuBinu
444
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53461740%2fsql-server-management-studio-results-scrolling%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Not directly achievable through SSMS interface but you can try something like the following.
First, determine which row number you'd like to jump to (index starts at one) and execute your query with the OFFSET and FETCH NEXT statements
SELECT * FROM Expense ORDER BY Id ASC OFFSET 4 ROWS FETCH NEXT 1 ROWS ONLY
OFFSET means how many rows you'd like to skip from the top, FETCH NEXT determines how many rows to display after the offset.
You can select the first row after skipping 20 rows (in other words, obtaining row 21), do the following
SELECT * FROM Expense ORDER BY Id ASC OFFSET 20 ROWS FETCH NEXT 1 ROWS ONLY
Not the best way of doing it, did not consider performance of such approach. But the easiest to achieve what you are looking for.
Another way could be executing the full query in Excel and use Ctrl + G to go to specific row number.
answered Jan 4 at 14:05
Ozan GuncelerOzan Gunceler
848510
add a comment |
Not directly achievable through SSMS interface but you can try something like the following.
First, determine which row number you'd like to jump to (index starts at one) and execute your query with the OFFSET and FETCH NEXT statements
SELECT * FROM Expense ORDER BY Id ASC OFFSET 4 ROWS FETCH NEXT 1 ROWS ONLY
OFFSET means how many rows you'd like to skip from the top, FETCH NEXT determines how many rows to display after the offset.
You can select the first row after skipping 20 rows (in other words, obtaining row 21), do the following
SELECT * FROM Expense ORDER BY Id ASC OFFSET 20 ROWS FETCH NEXT 1 ROWS ONLY
Not the best way of doing it, did not consider performance of such approach. But the easiest to achieve what you are looking for.
Another way could be executing the full query in Excel and use Ctrl + G to go to specific row number.
answered Jan 4 at 14:05
Ozan GuncelerOzan Gunceler
848510
add a comment |
Not directly achievable through SSMS interface but you can try something like the following.
First, determine which row number you'd like to jump to (index starts at one) and execute your query with the OFFSET and FETCH NEXT statements
SELECT * FROM Expense ORDER BY Id ASC OFFSET 4 ROWS FETCH NEXT 1 ROWS ONLY
OFFSET means how many rows you'd like to skip from the top, FETCH NEXT determines how many rows to display after the offset.
You can select the first row after skipping 20 rows (in other words, obtaining row 21), do the following
SELECT * FROM Expense ORDER BY Id ASC OFFSET 20 ROWS FETCH NEXT 1 ROWS ONLY
Not the best way of doing it, did not consider performance of such approach. But the easiest to achieve what you are looking for.
Another way could be executing the full query in Excel and use Ctrl + G to go to specific row number.
answered Jan 4 at 14:05
Ozan GuncelerOzan Gunceler
848510
Not directly achievable through SSMS interface but you can try something like the following.
First, determine which row number you'd like to jump to (index starts at one) and execute your query with the OFFSET and FETCH NEXT statements
SELECT * FROM Expense ORDER BY Id ASC OFFSET 4 ROWS FETCH NEXT 1 ROWS ONLY
OFFSET means how many rows you'd like to skip from the top, FETCH NEXT determines how many rows to display after the offset.
You can select the first row after skipping 20 rows (in other words, obtaining row 21), do the following
SELECT * FROM Expense ORDER BY Id ASC OFFSET 20 ROWS FETCH NEXT 1 ROWS ONLY
Not the best way of doing it, did not consider performance of such approach. But the easiest to achieve what you are looking for.
Another way could be executing the full query in Excel and use Ctrl + G to go to specific row number.
answered Jan 4 at 14:05
Ozan GuncelerOzan Gunceler
848510
answered Jan 4 at 14:05
Ozan GuncelerOzan Gunceler
848510
answered Jan 4 at 14:05
Ozan GuncelerOzan Gunceler
848510
answered Jan 4 at 14:05
Ozan GuncelerOzan Gunceler
848510
848510
add a comment |
add a comment |
There is no direct option for easy scrolling. You need to filter the result or export/copy the result to excel.
Usually I will copy the result to excel. This will give a clean look and also we can filter the result if needed in excel. :)
answered Jan 4 at 18:44
BinuBinu
444
add a comment |
There is no direct option for easy scrolling. You need to filter the result or export/copy the result to excel.
Usually I will copy the result to excel. This will give a clean look and also we can filter the result if needed in excel. :)
answered Jan 4 at 18:44
BinuBinu
444
add a comment |
There is no direct option for easy scrolling. You need to filter the result or export/copy the result to excel.
Usually I will copy the result to excel. This will give a clean look and also we can filter the result if needed in excel. :)
answered Jan 4 at 18:44
BinuBinu
444
There is no direct option for easy scrolling. You need to filter the result or export/copy the result to excel.
Usually I will copy the result to excel. This will give a clean look and also we can filter the result if needed in excel. :)
answered Jan 4 at 18:44
BinuBinu
444
answered Jan 4 at 18:44
BinuBinu
444
answered Jan 4 at 18:44
BinuBinu
444
answered Jan 4 at 18:44
BinuBinu
444
444
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53461740%2fsql-server-management-studio-results-scrolling%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Can you please define "large number of results" ? millions? a couple of millions? If that is the case, SSMS may not be the right way of viewing such number of records
– Ozan Gunceler
Jan 4 at 7:43
1
I agree with @OzanGunceler: If you're scrolling through a large amount of results in SSMS, trying to find a specific row, I think you'd be better off revising your query (as in his answer). You can also save your results to a CSV file, and then open it up in Excel.
– Zack
Jan 4 at 14:36
This is typically less than 50K records. Definitely agree on changing the query however, in this case it's an debug/error log so for troubleshooting reasons you need to see the records as they are recorded.
– wilbev
Jan 5 at 22:06