Viewing 15 posts - 4,171 through 4,185 (of 4,745 total)
each lock that SQL takes out uses up a small amount of memory (cannot remember how much - something like a few KB). The upper limit of no of locks...
---------------------------------------------------------------------
October 12, 2008 at 6:36 am
no problem, google the sp_help_revlogin stored procedure for best way to transfer over logins along with the users in the database whilst maintaining the SID values.
---------------------------------------------------------------------
October 11, 2008 at 3:12 pm
sorry, a compatability level of 80 does not mean you can restore a 2005 backup to a sql 2000 instance.
---------------------------------------------------------------------
October 11, 2008 at 3:06 pm
if its a backup from a SQL sefver 2005 you will not be able to restore it to a SQL2000 instance. Restore it to a a SQL2005 instance first and...
---------------------------------------------------------------------
October 11, 2008 at 2:26 pm
it certainly sounds like an orphaned user problem, so probably yes.
Connecting to the database is a two level thing, with the login in the master database to determine the ability...
---------------------------------------------------------------------
October 11, 2008 at 2:09 pm
strikes me if you are not going to use the DBMPW to create the database maintenance jobs, then avoid SSIS altogether, its not the best tool for the job. Keep...
---------------------------------------------------------------------
October 10, 2008 at 10:13 am
there is a column 'rowmodctr' in sysindexes which tracks the no of updates since the last update stats. Pretty sure this is what SQL uses for auto_update.
You could use this...
---------------------------------------------------------------------
October 9, 2008 at 4:10 pm
from memory the solution to this is something unexpected like untick the enforce password policy opton before unlocking the account on the status tab in login properties
---------------------------------------------------------------------
October 9, 2008 at 3:33 pm
this is most likely a bug. there have been lots of problems with cleanup tasks in maintenance plans in SQL 2005. You want to be at least at version 9.00.3054...
---------------------------------------------------------------------
October 8, 2008 at 3:31 pm
BCLynch (10/8/2008)
I took a maintenance plan (conencted to SSIS) end exported it to a file. I connected to a clean sql server and imported the dtsx file.
This created...
---------------------------------------------------------------------
October 8, 2008 at 10:15 am
Michael.varriale (10/7/2008)
I 'think' I need to set up a cluster with nodes in different cities for dr.
I have a lot of experience with clustering in the same...
---------------------------------------------------------------------
October 7, 2008 at 9:32 am
I think the agent XPs setting may be your real problem.
try running this via SSMS to permanatly set this on:
sp_configure 'show advanced options', 1
GO
RECONFIGURE
GO
sp_configure 'Agent XPs', 1
GO
RECONFIGURE
GO
---------------------------------------------------------------------
October 7, 2008 at 3:58 am
In the circumstances you describe with just one diff backup and one log backup, there is no reason at all why you should not just restore the full backup then...
---------------------------------------------------------------------
October 4, 2008 at 12:50 pm
microsoft are just bringing out Hyper-V, maybe they will support on that!
---------------------------------------------------------------------
October 3, 2008 at 11:12 am
Virtualised servers are known to have performance issues when supporting intensive applications, and this can include SQL server databases. so in terms of supporting busy SQL applications, vmware is not...
---------------------------------------------------------------------
October 3, 2008 at 10:32 am
Viewing 15 posts - 4,171 through 4,185 (of 4,745 total)