Viewing 15 posts - 211 through 225 (of 270 total)
You will need to allow the LocalSystem account the appropriate logon rights to SQL Server. To achieve this, do the following:
' The LocalSystem is known as [NT...
February 27, 2006 at 11:48 pm
I believe there are a number existing on this site; however, you can start having a look at this one:
http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=451
February 27, 2006 at 6:27 pm
Please following these instructions as is:
February 23, 2006 at 10:26 pm
The msdb database contains meta-data information including sql server agent jobs (when you create scheduled jobs), DTS packages, Replication, etc. So you can see that SQLSERVERAGENT will need access to...
February 23, 2006 at 9:44 pm
Have you tried closing EM and then open up a sql connection using QA?
February 23, 2006 at 7:33 pm
This error message is quite common when trying to restore a database. I would normally have a script handy that kills all active connections (spids) to a database before restoring.
BOL...
February 23, 2006 at 7:22 pm
BOL stands for Books OnLine. You can access it through Query Analyser (QA) - Help Menu/[Transact SQL Help].
Try setting the database to SIMPLE recovery mode, execute CHECKPOINT and then execute...
February 22, 2006 at 10:09 pm
I believe DBCC SHRINKFILE() with the EMPTYFILE option should do the trick. Refer to BOL for more info.
February 22, 2006 at 8:50 pm
You have two options:
Implement this login in the appropriate insert and update stored procedures, or use an instead of trigger for insert and update.
February 22, 2006 at 8:45 pm
Objects created in a database are context sensitive, unless you qualify it with dbo.
Say a user kevin, who is a member of the fixed database role db_owner but not...
February 22, 2006 at 7:36 pm
It appears to be a summary of the time it takes to process the log file during the restore:
1 page is 8kB in size, so
6938 pages makes 55.5MB (ie. 6938*8/1000),...
February 22, 2006 at 5:21 pm
Have you tried using profiler to get some idea of what CPU, memory and disk usage are for your new server? This will give the user group a bit more...
February 21, 2006 at 10:16 pm
You can, but only in conjunction with the SELECT INTO statement, e.g.
SELECT IDENTITY(int, 1,1) AS ID_Num
INTO NewTable
FROM OldTable
See BOL for more info.
February 21, 2006 at 6:12 pm
Try using QUOTENAME().
February 21, 2006 at 6:07 pm
Viewing 15 posts - 211 through 225 (of 270 total)