Viewing 15 posts - 256 through 270 (of 285 total)
Try this. By the way, I used Query Analyzer in this example because it is easier to describe than all the clicking that needs to be done in Enterprise Manager.
Jon
---------------------
--...
July 3, 2003 at 8:34 am
Sorry... I think this was caused by a HOSTS file setting. Duh!!!!!!!!!!!!!!!!!!! That's what I get for no being able to finish some testing I started a while back.
Moderator, please...
July 2, 2003 at 7:28 am
Here is a copy of the wheel that I re-invented, but I'm not particularly happy with the code. Anyone have any better ideas?
Thanks,
Jon
create function DBA_FormatNumericData
(
@floatfloat,-- An integer value that will...
June 25, 2003 at 1:21 pm
FYI -
We don't install Outlook on our servers because of the associated security patch problems, but I ran across some freeware a little while back that sends e-mail without using...
June 23, 2003 at 8:38 am
Here is something that works for me on SQL 6.5 and 2000 (I didn't test it with 7.0):
Jon
-----------------------
use TestCorrupt
go
/*******************************************************************************
*
*Create a test table
*
********************************************************+**********************/
create table junk
(
col1int,
col2char(1),
col3varchar(50),
col4datetime
)
create index Junk_IDX1 on Junk
(col1)
go
/*******************************************************************************
*
*Allow updates to...
June 23, 2003 at 8:12 am
Allen_Cui,
quote:
Have you tested the restoration without 'replace' option when the database does not exist and underlying NTFS files do *not* exist?
June 11, 2003 at 11:40 am
I should have mentioned that in the period of time that SQL Server is twiddling with the NTFS files, the activity light goes off on the tape drive (in the...
June 10, 2003 at 7:45 am
I think you are right. It seems like I read something about that a while back. Do you have any ideas on how to "encourage the process along" a bit?...
May 20, 2003 at 10:45 am
Robert,
I suspect that is why we do not tend to see problems with Auto Shrink as well. "Purge" does not seem to be in our Developers' vocabulary.
May 14, 2003 at 5:45 am
No, we removed replication from our environment for the same reason--it can just be a real pain to locate the source of problems when there are many databases being replicated.
...
May 9, 2003 at 12:21 pm
srini_kris,
In function, our solution is virtually identical to log shipping, but the restores are handled in a single script, without copying backup files multiple times over the network. When something...
May 9, 2003 at 11:46 am
We tried replication under SQL 6.5, and, as I recall, replication would not push DDL (i.e., table and stored procedure) changes from the source server to the destination server. I’m...
May 7, 2003 at 8:42 am
By the way, several people alluded to shrinking the databases during off hours. Would anyone care to post the syntax they use?
Thanks
May 7, 2003 at 8:19 am
I agree that Auto Close is a silly option. It potentially causes more headaches than it is worth. Rdb (purchased by Oracle several years ago) has the same goofy feature.
On...
May 7, 2003 at 8:15 am
David.Poole,
Point well taken. Better documentation would obviously help. And certainly, office politics are a factor. However, I still maintain that the tools for debugging stored procedures are primitive at best...
April 22, 2003 at 7:18 am
Viewing 15 posts - 256 through 270 (of 285 total)