Viewing 7 posts - 1 through 7 (of 7 total)
The -g parameter is a start-up flag. You can set it by running SQL Server Configuration Manager (in the Configuration Tools sub-menu) and selecting SQL Server Services in the...
July 2, 2010 at 3:11 am
It's probably a good time to come back to this thread and let you know how our issue panned out. We thought that the -g flag had solved the...
February 19, 2010 at 6:50 am
I'm probably tempting fate, but I think we've solved this issue; we've been running over a week without any problems, which beats any of our previous experiments.
We have quite a...
March 24, 2009 at 4:26 am
Hi Andy,
We've been encountering the same issue in similar circumstances, albeit we're only using Windows 2003 Standard Server. We're migrating our SQL Server 2000 systems, that have been running...
March 11, 2009 at 8:41 am
Is there an assumption that the database collation is case-insensitive?
If you are running a case-sensitive instance, only LIKE '[0-9,A-Z]%' gives a positive answer with this example, but wouldn't work...
June 2, 2005 at 1:55 am
Is this a case of bad copy and pasting from MSDN? See:
http://msdn.microsoft.com/msdnmag/issues/05/06/SQLServerSecurity/default.aspx
Surely the real answer is
EncryptByCert(Cert_ID('MyUserCertificate'), @data)
May 27, 2005 at 4:25 am
A reboot on its own doesn't change the recovery mode of msdb. On our model (2k SP3) the mode changes to simple when SQLAgent starts.
I would have thought most installations...
November 2, 2004 at 4:31 am
Viewing 7 posts - 1 through 7 (of 7 total)