Viewing 15 posts - 2,311 through 2,325 (of 2,435 total)
... adding to the "Minor quibble" ... I'd prefer to call it a 'best practice'. Why not take it one step further and declare the 'limit' for your 'while loop' as...
March 22, 2005 at 12:30 pm
I do not know of a 'clean' way to do this in SQL2K. You'll have better luck in SQL2K5 though with DDL triggers to perform this type of audit.
March 22, 2005 at 12:26 pm
Lots of good discussion here. However the bottom line is that the solution must meet the 'business' needs of the user community. There may or may not be room for...
March 22, 2005 at 11:28 am
'sa' is the logical choice. domain/username database creators/owners have caused minor issues when the AD accounts are removed for the database on it's original server (ownership of 'unknown' or 'null')....
March 22, 2005 at 10:51 am
Have you checked active directory ? Specifically the 'Account' tab, 'Log On To' button ?
March 21, 2005 at 9:08 am
A database user cannot be deleted if it owns objects in the database. Take one user and execute:
exec sp_dropuser 'username'
or
exec database_name..sp_dropuser 'username'
The error message from this should confirm...
March 18, 2005 at 5:01 pm
Here's how it works:
1) The before and after image of the changed row are written to the transaction log.
2) The page in memory that contains the row is updated.
3) The...
March 18, 2005 at 3:35 pm
separate proc yes, conditional execution though.
March 17, 2005 at 1:27 pm
All I can say is: "SQL Reads in 'extents' (64kb) and writes in 'pages' (8kb)". Al the rest is hardware tuning. You might want to perform some I/O benchmarking.
March 17, 2005 at 12:00 pm
Sounds quite 'draconian' to me. I've always had 'Local Admin' on my SQL Servers. Prior to RDP, console access as well. The list of companies I've traversed reads from fortune...
March 17, 2005 at 11:57 am
Before going in too deep with 'profiler', why don't you try using:
sp_who
sp_lock
sp_who2
sp_lock2
It may be something really obvious.
March 17, 2005 at 11:45 am
A little code snippetto make the change (I'd probably restart SQL afterwards as well).
---
--- fix_db_sid.sql
---
use master
go
exec sp_configure 'allow updates',1
go
reconfigure with override
go
update sysdatabases
set sysdatabases.sid = s.sid
from syslogins as s
where sysdatabases.name...
March 17, 2005 at 11:38 am
Since it's a MS environment I'd opt for Windows scripting or VB (although most of what you speak about can be done in Transact SQL and a few simple .cmd...
March 17, 2005 at 10:00 am
I just encountered this type of issue in 'beta' SQL 2K5 admin training a couple of weeks ago. The 'eval' version expired on morning 2 of a 3 day course. We worked...
March 15, 2005 at 11:30 am
I've run into similar situations. We use domain user accounts (one for each service) in a domain group which is in the Local Administrators group on each SQL Server. We...
March 11, 2005 at 3:26 pm
Viewing 15 posts - 2,311 through 2,325 (of 2,435 total)