Viewing 15 posts - 76 through 90 (of 128 total)
Reboot the server. Have a look in Control Panel and see if the SQL Services exist and under what account they are running under. Start them if they aren't started.
March 3, 2005 at 3:39 am
Just a bit more detail. Server network utility define what network protocols you can use to connect to the SQL Server eg TCP and port 2020.
Client network utilities define what...
March 2, 2005 at 3:05 am
In a production environment it is the businesses call on its recoverability - not the DBAs, in line with the SLAs. But as the DBA you need to understand what...
March 2, 2005 at 2:57 am
If you can start SQL Server in minimal mode from the command line (-f) then use the script that is on the install CD to recreate the model DB. Problem...
March 2, 2005 at 2:52 am
There ae a large number of reasson for this error. Search the microosft knwoledge base for 80004005 - example KB306586
March 2, 2005 at 2:48 am
Any attachmentst to the email that may be blowing up size? Had something similair when Exhange didn't like anything greater than 1 Mb
March 2, 2005 at 2:37 am
Upgrade path is very simple. I did this on 8 production servers - with a reboot (not required - biut I did just to make sure) and then reapplied SP3a and...
March 2, 2005 at 2:28 am
With SQL 6.5 the SQL Mail component was not as seamless as it is now. Make sure that the SQL Services are running under their own account and the Outlook...
March 1, 2005 at 3:46 am
I had a client who wanted this sort of recovery. All I could end up doing was backing up the database, restoring it to another replica database, truncating all tables...
March 1, 2005 at 3:42 am
Check to see if the data file or the log file is growing. If the log is growing them it may be because the recovery mode is full and the...
February 27, 2005 at 8:55 pm
The only way to get exclusive use of a tabe is to use a tablockX locking hint.
You will not be granted the lock until all other users have finished accessing...
February 27, 2005 at 8:51 pm
You don't need the ID column as the customer code as a primary key will enforce unqiueness and not null.
You can make an identity column larger - just change it...
February 27, 2005 at 8:43 pm
This will be made easier if the FURTEMP server has the same disk config as FURSQL, then you don't even need to change the physical file location when you restore.
February 25, 2005 at 2:04 am
You can encrypt stored procs and views - although it can be unencrypted with readily available scripts. Yukon has better encryption techniques - but who can wait that long
February 25, 2005 at 2:00 am
Viewing 15 posts - 76 through 90 (of 128 total)