Viewing 15 posts - 421 through 435 (of 458 total)
99% of the scripts we use are in house or customized from sites like SQLServerCentral.com
That being said, there are a couple third party tools that are worth their weight in...
November 21, 2008 at 7:23 am
Steve Jones - Editor (11/19/2008)
Seeing the paper result, but not holding it is interesting. And it's a good compromise, perhaps the best we'll ever get.
I read...
November 20, 2008 at 11:03 am
Jeff Moden (11/19/2008)
Gaby A. (11/19/2008)
November 20, 2008 at 7:02 am
Thanks everybody, given me food for thought. Unfortunately this DB was set up before I joined my company but but at least in the future, if I get any...
November 19, 2008 at 8:20 am
Hmmm...we just had a national election here in Canada, and we just used pencil and paper. Granted, ours is a parliamentary system where we did not elect a President...
November 19, 2008 at 7:47 am
nelsonj (11/13/2008)
November 17, 2008 at 8:37 am
RML51 (11/14/2008)
I think I have a pretty good memory. I have my credit card number memorized...
November 17, 2008 at 8:27 am
Jeff Moden (11/13/2008)
November 17, 2008 at 8:24 am
After you create the script, run this command from within master:
exec sys.sp_MS_marksystemobject 'sp_YOUR_SCRIPT_HERE'
which allows you to run it from any database.
November 17, 2008 at 7:17 am
This is also a good book that the DBA's in my department refer to:
November 17, 2008 at 7:15 am
Try this one as well: http://www.sqlservercentral.com/scripts/Administration/63841/
It's one I recently used to audit a server for our Internal Auditors.
November 17, 2008 at 7:12 am
I found this as a possible solution, using shrinkfile, from http://blog.sqlauthority.com/2007/04/01/sql-server-tempdb-is-full-move-tempdb-from-one-drive-to-another-drive/
[font="Courier New"]use tempdb
dbcc shrinkfile(templog, 0)
backup log tempdb with Truncate_Only
dbcc shrinkfile(templog, 0)
[/font]
Avoid the hassle of shrinkdatabase. But maybe have the...
November 14, 2008 at 6:27 am
MANU (11/12/2008)
November 12, 2008 at 1:50 pm
Okay...the proper/full workaround I came up with was:
create table #TOrphans
(
DBName varchar(128) collate SQL_Latin1_General_CP1_CI_AS,
UserName sysname collate SQL_Latin1_General_CP1_CI_AS
)
exec sp_msforeachdb
'use ?;
insert into #TOrphans(DBName, UserName)
select db_name() collate SQL_Latin1_General_CP1_CI_AS, Name collate SQL_Latin1_General_CP1_CI_AS from dbo.sysusers
where name...
November 12, 2008 at 11:03 am
I agree with Brandie, sometimes the most useful scripts are surprisingly simple and elegent. Will make my reporting to the Loss Prevention folks more manageable.
November 12, 2008 at 7:27 am
Viewing 15 posts - 421 through 435 (of 458 total)