2 回答
- 最新
- 投票最多
- 评论最多
0
This was a user rights issue : 1°) SQL Server username needs to have usermapping with db_datareader & public on SQL Server database 2°) SQL Server username used by Lambda function should be able to read in table : SYS.DM_DB_PARTITION_STATS :
USE [database_name];
GRANT VIEW DATABASE STATE TO [user_name];
3°) maque sure that schema to be read (ex : "dbo") has issqluser column value at "1" in table : sys.sysusers
已回答 1 年前
0
it may be related with the JDBC Driver you are using or the Connection String try to write queries like database.schema.tablename for SQL Server like database.dbo.tbl_name
相关内容
- AWS 官方已更新 3 个月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 3 年前
Ni Sedat, just a SQL server user rights issue.