|
If I give read-only access to a SQL Server login, does that mean they cannot call stored procedures that CRUD data?
What I'm looking for is the ability for users to:
1. Read the database,
2. Execute stored procedures that CRUD data.
But NOT run any DDL. Meaning they cannot change table structures or stored procedures.
I'm sure there must be a way to configure this.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
So long as the user has permission to execute the stored procedure, and the stored procedure and the tables it references have the same owner, then it will work even if the user doesn't have any permissions on the referenced tables.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Thanks, Richard!
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Attempting to recover from the Azure disaster I downloaded the developer and then the express versions of SQL Server 22. Both failed to install because of a missing/incorrect msoledbsql. I then downloaded the dll and installed it before attempting to reinstall, it still failed on the same issue.
I tried the same with 2019 version with the same issue.
Any suggestions as to how to get around the problem?
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
|
Excellent - that resolved the issue, thanks. Now any chance you can shake a person out of Azure 
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
I have discovered that in T-SQL for Sql Server 2022, if I run a stored procedure that happens to call another stored procedure that returns a result set, then the server returns both result sets to my application.
How can I, within T-SQL, specify that the result set of an embedded stored procedure call is not part of the return to the client? Is there a way to specifically choose?
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
For a single resultset, you may be able to use INSERT .. EXEC to dump the resultset into a temporary table / table variable.
DECLARE @tmp TABLE ( ... );
INSERT INTO @tmp EXEC yourStoredProcedure ...; But if you control the other stored procedure, a cleaner option would be to add another parameter to suppress the output.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Thanks, Richard. I'm frankly surprised that there's no documented way to return only specific result sets. I'll probably end up using the additional parameter to suppress output.
Cheers.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Is there any tool/solution to export the tables and then data from SQL Server to SQLite?
|
|
|
|
|
|
I know that tools, they simply don't run on my machine. They are C# apps and probably needs some net framework to install. But instead of digging to see why they are not run, I am concentrating to a reliable tool/solution (which I didn't find yet).
|
|
|
|
|
So basically, you've put as much effort into getting the tools you've found to run as you have into asking your question: ie: none. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
No, that's not true. For instance, I have installed a net framework for a C# application, but still doesn't run, so, what can I do? To find out why that application is not working?
modified 25-Jul-24 5:17am.
|
|
|
|
|
_Flaviu wrote: No, that's not true.
I suggest you re-read your own messages, remembering that nobody here can see your screen, access your computer, or read your mind. Do you really think you've put enough effort into describing the problem(s) you're having for someone to be able to help you?
From my perspective, your thread so far reads as:
Summary: I want a tool to do «x».
I've tried some tools - I won't tell you which - and none of them worked, probably because I didn't read the system requirements or install the prerequisites.
Rather than trying to fix the errors, or tell you what the errors are and ask for help with fixing them, I've added those tools to a secret shitlist of "unreliable tools".
I now demand that someone provide me with a tool that isn't on my secret shitlist - and no, I won't tell you what's on it! - that works first time, with zero effort on my part.
Remember, the effort someone is going to put into answering your question is directly related to the effort you put into asking it. If we have to keep dragging tiny snippets of information out of you in dribs and drabs, then why should we bother trying to help?
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
|
I have succeeded to migrate a table from SQL Server by importing it the table to Excel, and from Excel sheet to SQLite using Python. The relations between tables I guess I should do it manually.
|
|
|
|
|
Insufficient key column information for updating or refreshing problems is displayed
|
|
|
|
|
|
Aside from the fact that you're still using software which is a whole quarter of a century out-of-date, and has been officially "dead" for over two decades, you haven't provided any information that could be used to help you.
Rather than giving us your "summary" of the error message, provide the full error message, and explain precisely what you were doing when you saw it. If it's cause by code, then show the relevant parts of your code.
You also need to explain what you have tried and where you are stuck.
With the limited information provided, the only "help" we can offer is to paste your error into a search engine.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: Aside from the fact that you're still using software which is a whole quarter of a century out-of-date,
Just noting that VB6 is still 'good' at least through EOL for Windows 11. Won't be improved but it won't stop working either.
Support Statement for Visual Basic 6.0 | Microsoft Learn[^]
|
|
|
|
|
By that argument, maybe we should all start our next projects in COBOL? 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: all start our next projects in COBOL?
To be fair COBOL has new spec in 2023 and one can create AWS Lambdas with it also.
So perhaps Pascal is a better comparison?
|
|
|
|
|
Then ALGOL-60 would be much better! 
|
|
|
|
|
jschell wrote: Just noting that VB6 is still 'good'
And that's when the violent vomiting started.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
