Viewing 15 posts - 35,026 through 35,040 (of 39,723 total)
Wow, I never noticed that. That's rather interesting and I have confirmed on multiple servers.
This "bug" does make the search for blank passwords much easier
April 6, 2004 at 10:41 am
Haven't seen this. I assume you just copied from a "good" server to fix it.
April 6, 2004 at 10:26 am
All the left joins will kill you because you have to hit EVERY single row in these tables, i.e. table scans.
If you can and there is not a lot of...
April 5, 2004 at 10:56 am
VAX !!?!?!!! Nightmares are returning ![]()
The suggestions above are great. I'd use DTS to script out the moves using one of the techniques above.
April 5, 2004 at 10:45 am
This runs on the server, so be sure the path/file is valid ON THE SERVER not your workstation.
April 5, 2004 at 10:36 am
I understand the part about testing/validating and agree with it, but sometimes that is your only option. I run 24x7 Unix databases on DB2 and sometimes we have to bite...
April 5, 2004 at 10:35 am
Inside SQL Server 2000 (Kalen Delaney)
The Guru's Guide to SQL Server Architecture and Internals - Ken England.
April 5, 2004 at 10:26 am
We've had similar issues with using IBM's Client Access drivers for the AS/400. The only resolution was to reboot the server, both from IBM and MS. The memory size of...
April 5, 2004 at 10:20 am
Systernals has PsTools which will allow you to psexec( execute a remote command) on another computer.
April 5, 2004 at 10:12 am
Set a DSNless connection to a full qualified domain name. Like mydsn.sqlservercentral.com as the server name. Then change the name in DNS when you migrate.
April 2, 2004 at 3:22 pm
Are you sure they are being backed up? SQL Server will hold the mdf and ldf open just like Word, Excel, whatever. Most backup software doesn't handle this or doesn't...
April 2, 2004 at 3:21 pm
or
create trigger mytrig on mytable for update
as
insert myhistory( myval1, myval1)
select i.myval1, i.myval2
from inserted i inner join deleted d on i.pk = d.pk
where i.myval1 <> d.myval1
repeat.
April 2, 2004 at 3:15 pm
You need to be able to run the app without interactivity. Can you modify to take parameters?
BTW, using a trigger is a bad idea:http://www.sqlservercentral.com/columnists/sjones/worstpracticetriggeringexternalevents.asp
April 2, 2004 at 3:11 pm
Deny should work. Have they disconnected and reconnected? Not that it should matter.
I'd make a role that has DENY access and add them instead of their individual permissions.
April 2, 2004 at 3:09 pm
Not sure you can clear the roles, but I'd change to a strong one time password and then rotate that every 30 days.
Alternatively, if you can, disable SQL Auth.
April 2, 2004 at 3:08 pm
Viewing 15 posts - 35,026 through 35,040 (of 39,723 total)