Viewing 15 posts - 35,431 through 35,445 (of 39,769 total)
today's headline as well
http://www.sqlservercentral.com/columnists/ckempster/sendingalertsviaacustomsmtpprocedure.asp
January 13, 2004 at 10:44 am
Write a script to delete the account or change to deny access in 10 days and schedule it.
January 13, 2004 at 10:43 am
A few thoughts : http://www.sqlservercentral.com/columnists/sjones/whodoyouhire.asp
Feel free to steal some QOD questions if you want. They will at least give you an idea of this person's knowledge. I'd put them...
January 13, 2004 at 10:40 am
Agree that if the load is expected to be high, SQL provides much better concurrency over Access. Access is best and cheaper for small numbers of users.
January 13, 2004 at 10:31 am
Cookies were required with the old software and we are running in a dual ASP.NET / classic ASP environment now.
We might be able to eliminate them in the future, but...
January 13, 2004 at 10:29 am
January 12, 2004 at 2:57 pm
I would agree with above. The suspect flag is just a bit setting in sysdatabases. If it keeps getting reset, then likely the issue has not been resolved and PSS...
January 12, 2004 at 2:55 pm
Run profiler and see what is hitting the server.
January 12, 2004 at 1:52 pm
Your only choice is a per CPU license. As soon as you authenticate anonymous users, whether directly, through a website, or using MTS, you must license per CPU. Only when...
January 12, 2004 at 1:49 pm
Not sure since I don't use Log Shipping, but this message indicates that a log is being restored out of order. Or one was missed. I'd check there.
January 12, 2004 at 10:33 am
What type of replication?
Most books on SQL Server have a decent tutorial on getting started with replication. Brian Knight's SS2K for Experienced DBAs has a good explanation (ISBN:0072227885 )
January 12, 2004 at 10:11 am
The only real way to automate this is with a trigger. But the trigger can be really simple and update the same table as mentioned above, then load your "backup"...
January 12, 2004 at 10:07 am
You also need to be sure that you know why the database went suspect. Check the error log for a reason.
You can clear the suspect flag as well with
sp_resetstatus <db...
January 12, 2004 at 10:02 am
While we're not really looking at doing that for a number of reasons, can you list the issues with the new forums? It's a big change for me as well,...
January 12, 2004 at 9:47 am
I use a batch file (*.cmd) that calls
isql -S ServerA -E -Q"sp_password null, new, sa" >> change.txt
with a line for each server, add a server add a line, change the...
January 9, 2004 at 2:58 pm
Viewing 15 posts - 35,431 through 35,445 (of 39,769 total)