Viewing 15 posts - 706 through 720 (of 1,248 total)
I cannot remember exactly. But here are some points you may check.
1. Open your connection or recordset in client side;
2. After your strSQL in the OPEN statement, add another switch....
January 31, 2008 at 2:24 pm
How about right-click the Replication folder, and then select Generate SQL Script ...?
January 31, 2008 at 10:08 am
Just personal point of view.
I do not think that it caused by different versions. Did you check the timeout settings on other SQL Servers?
January 31, 2008 at 9:42 am
If you would like to have full backup only, you should set the recovery mode to SIMPLE. Otherwise, your log file will keep increasing. Although this rate may not be...
January 31, 2008 at 9:35 am
I think it is an issue on the application interface. Before a user logoff, the application should close the connection. Otherwise, the session on SQL Server will remain there until...
January 31, 2008 at 9:30 am
Yes. When you apply service pack, you can choose what instance(s) you would like to apply the service pack.
January 30, 2008 at 3:45 pm
GilaMonster:
I agree with you that modification of system databases is not recommended, generally speaking.
January 30, 2008 at 9:50 am
It is a good question. Unless your ten data files are in different physical drives or arrays, your backup will not be faster.
January 29, 2008 at 8:38 pm
Ray:
If you have full backup of a database, the SQL Server system may create a log file for you.
January 29, 2008 at 8:31 pm
Could you try to attach your file as a user database with different name, then make a backup, and then restore/overwrite it on msdb?
January 29, 2008 at 7:29 pm
How about this one. You only need to make your change accordingly.
CREATE DATABASE myDB
ON
PRIMARY ( NAME = myDB1,
FILENAME = 'c:\myDB1.mdf',
...
January 29, 2008 at 7:22 pm
Could you open your master..sysdatabases, modify the column filename to the locations of your mdf and ldf files? Then, restart your services?
January 29, 2008 at 2:40 pm
Let us assume you have authority to do it.
By default, when you try to modify a stored procedure in a script, you may not see its owner. But there is....
January 29, 2008 at 1:21 pm
SQL 2000 SP4 has a bug resticting memory to be used with 4 GB. Did you apply hot fix? You may also need to enable AWE.
January 29, 2008 at 12:47 pm
Viewing 15 posts - 706 through 720 (of 1,248 total)