Tag Info

New answers tagged

4

It looks like you'll need to change the user's default database, as it appears this is currently set to DB1, which no longer exists. exec sp_defaultdb @loginame='user1', @defdb='DB2' OR ALTER LOGIN <login_name> WITH DEFAULT_DATABASE = <default_database>


1

As Jonathan stated and the link shows CONTROL SERVER is required prior to SQL Server 2012 to create an Extended Event session. The ALTER ANY EVENT SESSION permission prior to SQL Server 2012 only allowed a user to start/stop a session, or change a current session; it will not allow them to create a session. CONTROL SERVER is required for that ability. If ...


0

I think you need to either qualify type with schema when using client account (CO_ADMIN.DOCPARAMETERTYPE_TABLE, not just DOCPARAMETERTYPE_TABLE ) or create a public synonym for the type.


1

I suggest you create a dedicated schema for this user (if it does not exist already), typically with the same name as the name of the role. CREATE SCHEMA this_user; REVOKE ALL ON SCHEMA this_user FROM public; GRANT USAGE ON SCHEMA this_user TO this_user; The default search_path in typical Postgres installations is "$user",public. So the new schema is ...


1

Yes it does, but that will turn into a maintenance headache down the road. Read http://en.wikipedia.org/wiki/Role-based_access_control for justification for assigning rights to roles over individual users. Simply create a role and assign users to it, and then grant privileges to that role. create role some_group; grant some_group to mary, bob, sue; ...


-1

Stop all SQL services, then go into SQL Server Configuration Manager and select SQL Server Services in the tree. Then go into Properties for the database engine service of interest and select the Advanced tab. Click the dropdown arrow on the Startup Parameters value, and add ;-m (semicolon, dash, m) to the end of the text. Click OK to exit the dialog box. ...


3

You could GRANT each existing user the special no-privilege USAGE privilege, which doesn't change their existing privileges but can be used to REQUIRE SSL for an existing user. USAGE can be specified to create a user that has no privileges, or to specify the REQUIRE or WITH clauses for an account without changing its existing privileges. — ...


5

From here If you have the PROCESS privilege, you can see all threads. If you have the SUPER privilege, you can kill all threads and statements. Otherwise, you can see and kill only your own threads and statements. You can also use the mysqladmin processlist and mysqladmin kill commands to examine and kill threads. See here for privilege ...



Top 50 recent answers are included