Viewing 15 posts - 151 through 165 (of 286 total)
You need to allow SQL Server Agent to use tokens (option available in SQL Server Agent properties). There is security risk associated with this: http://msdn.microsoft.com/en-us/library/ms175575.aspx.
May 30, 2010 at 9:14 pm
Hi,
By default job owner is login that created job and this is in most cases member of sysadmin role. Later the owner could be changed to the login that is...
May 28, 2010 at 2:58 pm
Before you detach database check which login mapped to dbo user in database, also run DBCC CHECKDB. When you detach database use @skipchecks = 'false' option to make sure statistics...
May 28, 2010 at 2:41 pm
It looks like tables (or schemas) ownership issue. I have never had this issue, but you can try to transfer ownership to another user http://technet.microsoft.com/en-us/library/ms187359.aspx%5B/url%5D.
May 23, 2010 at 9:57 am
You can use SSIS Transfer Jobs Task to copy jobs from one server to another:
http://www.sql-server-performance.com/articles/dba/ssis_transfer_jobs_task_p1.aspx
May 23, 2010 at 9:41 am
Try MSDB stored procedure:
sp_update_job @job_name = 'job_name', @owner_login_name ='login'
Make sure new login has permissions on SQL Server.
May 21, 2010 at 5:37 pm
Do you backup to the local disk or network location? Does SQL Server service account has access to the backup location?
May 21, 2010 at 5:34 pm
Also, make sure that you update databases statistics regularly.
May 21, 2010 at 5:28 pm
Don't drop the log file! There could be transactions that are not saved to the database. Try to query these DMVs to see if there are any active transactions: sys.dm_tran_locks,...
May 21, 2010 at 5:25 pm
Hi Juanita,
Does your table have any datetime columns that track when records have been created?
May 21, 2010 at 5:10 pm
You can compare the time of the largest transaction logs' backup with index optimization jobs schedules. For some of my databases log grows dramatically during index rebuild tasks.
May 19, 2010 at 5:30 pm
We've tried CommVault SQL Server agent backups, but decided to go back to the SQL Server native backups which backed up later as .bak files using CommVault.
The main reason was...
May 19, 2010 at 5:20 pm
There are no really rules about transaction log's sizing. It depends on too many factors. The best answer is the latest Paul Randal's Q&A publication in SQL Server Magazine: http://www.sqlmag.com/blogs/sql-server-questions-answered/sql-server-questions-answered/tabid/1977/entryid/12625/Default.aspx
May 19, 2010 at 4:54 pm
Sorry, I misstyped it:
FOR /F %a IN (srvList.txt) DO osql -S %a -E -d master -Q "EXEC sp_helpsrvrolemember 'sysadmin' " -n -h-1 -s , -w 1000 >> "output_SrvRoleMember.txt"
May 19, 2010 at 4:01 pm
Backup existing DB and restore it as NewNameDB. You will have to use MOVE option on restore to rename database files:
RESTORE DATABASE NewNameDB
FROM OldDB
WITH...
May 19, 2010 at 8:51 am
Viewing 15 posts - 151 through 165 (of 286 total)