In SSMS - under Databases >>mydatabase >>Security >>Users >>myusername, right click the username, select properties under database role...

This error occurred because none of the database mail...

check that you didn't check db_denydatareader DB role

You can see the current database mail configuration by using the following system functions

EXEC msdb.dbo.sysmail_help_configure_sp;

EXEC msdb.dbo.sysmail_help_account_sp;

EXEC msdb.dbo.sysmail_help_profile_sp;

EXEC msdb.dbo.sysmail_help_profileaccount_sp;

EXEC msdb.dbo.sysmail_help_principalprofile_sp;

Login failed for user usually means that your connection request was successfully received by the server name you specified, but the server is not able to grant you access for...

As the message already says, restore the database from the backup.

Or

- Detach the database

- Rename/Move the log file

- Attach the MDF database file without the LOG file; a new log...

Full backups do not break log shipping. The only things that cause the log to be truncated are log backups, an explicit truncate or a switch to simple recovery model

try the below query to get result in DD/MM/YY format.

select LEFT(convert(varchar(10), @date, 103),6) + Right(Year(@date)+ 1,2)

ALTER TABLE [dbo].[ table_name] DROP CONSTRAINT [fk_name]

Try DBCC CHECKDB with parameters REPAIR_REBUILD or REPAIR_ALLOW_DATA_LOSS to fix the corruption of your database.

If DBCC CHEKDB cannot help to solve the problem, then you can try database backup and...

Check out the following link to stop log file growth: http://blog.sqlauthority.com/2010/09/20/sql-server-how-to-stop-growing-log-file-too-big/

and to shrink log file you can take the help of this link: http://www.sqlserverlogexplorer.com/shrink-transaction-file/

...

Check out the following link hope this will help you: http://dba.stackexchange.com/questions/51489/sql-server-2012-restore-backup-to-new-db-name

CREATE TABLE dbo.foo (bar int PRIMARY KEY WITH (FILLFACTOR=90, IGNORE_DUP_KEY = ON))

GO

INSERT dbo.foo VALUES (1)

GO

INSERT dbo.foo VALUES (1)

GO

--gives

(1 row(s) affected)

Duplicate key was ignored.

(0 row(s) affected)

Take a look at this article: http://www.sqlservercentral.com/blogs/brian_kelley/2013/04/22/troubleshooting-sql-server-error-15517/

Only users with sysadmin rights can use xp_cmdshell exclusively others will get some or the other error.