Viewing 15 posts - 226 through 240 (of 49,571 total)
Permissions
Requires VIEW DEFINITION permission on the database and SELECT permission on sys.sql_expression_dependencies for the database. By default, SELECT permission...
March 27, 2018 at 3:06 pm
Key size or algorithm? 2008 doesn't support the same ones that 2014/2016 do.
March 27, 2018 at 3:04 pm
See the documentation:
https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-send-dbmail-transact-sql
March 27, 2018 at 2:15 pm
Can you give a reference for those 'standard' steps for splitting a partition?
March 27, 2018 at 1:29 pm
March 26, 2018 at 2:25 pm
March 26, 2018 at 9:35 am
Database Encryption keys are not, afaik, limited by edition.
What's the error that you're getting?
March 26, 2018 at 7:18 am
Master one of the aspects you already know, is another option
March 26, 2018 at 5:01 am
Errr... CROSS APPLY to the function will probably be what you're looking for, but I have no real idea because you haven't given enough details.
March 25, 2018 at 11:08 am
If you're using SQL 2008 R2, I'd suggest you stick with trace. While XE existed on 2008 R2, it was fairly limited. It became a lot more usable in 2012.
March 25, 2018 at 3:34 am
Always Encrypted is supported on Standard Edition.
https://docs.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2016
See the section RDBMS Security
March 25, 2018 at 3:09 am
They're not included in Express edition.
March 24, 2018 at 5:27 am
You can stop getting it by figuring out what app on the client specified is trying to connect to a DB that doesn't exist, because the root cause of this...
March 23, 2018 at 2:45 pm
Viewing 15 posts - 226 through 240 (of 49,571 total)