Tag Info

New answers tagged


You don't want your test database to retain the same internal id number as the production database. Hence it would be best to use RMAN's command DUPLICATE, because it sets a different id (and also a new database name). This command is specifically designed to do what you require.


Your regexp_replace() statement is invalid. It would work like this: SELECT regexp_replace(tbl, '('''')$', '' , 'g') FROM ( VALUES ('6''''') ,('6''''') ,('6''''') ,('20''''') ,('12''''') ,('18''''') ,('20''''') ,('8''''') ,('10''''') ,('''''') ,('''''') ) tbl(tbl) Your SELECT INTO statement is invalid. It would look like this: SELECT ...


If you've dropped all the tables, you could just drop the database and re-create it. It will be created with the default sizes and growth rates as defined by the model database. These may not be ideal (I don't find the defaults particularly useful in most scenarios), but you can change them. Unless you have a lot of things set up on this database (like ...


In SQL server the data and log files only grow automatically. If you deleted alot of data there will be empty space inside the file but SQL server will not shrink the file automatically because it expects more data to be added and growing the files is expensive. shrinking the file is also generally bad for indexes and stats but since you dropped all the ...


If you have the admin option over a role you can drop that role, even if you don't possess the drop role privilege or "own" the role, as in, you didn't create the role.


Microsoft SQL Servers do not allow the use of User Principle Name (UPN) addresses for service accounts. There is a post from a few years ago in Microsoft Connect and a more recent post: https://connect.microsoft.com/SQLServer/feedback/details/519008/upn-user-principal-name-as-services-account-name#details ...

Top 50 recent answers are included