Viewing 15 posts - 406 through 420 (of 497 total)
Hence the reason it's best to call PSS when doing that.
I still think the best solution would have been to do a backup prior to the upgrade and then...
September 16, 2003 at 3:20 pm
spireite,
While building recordsets for a single record may seem trivial. As soon as you multiply that creation over all the conceivable connections a web server could have it can really...
September 16, 2003 at 11:45 am
Yes,
I just found this work around myself. Here are the steps.
create a new database by same name and same physical filenames as the old ones ( save out the old...
September 16, 2003 at 11:30 am
Very nice article Andy! I think I would rather restore the backup that I would have created just prior to installing SP4 though as I think that would simply be...
September 15, 2003 at 5:49 pm
Look at the topic "Strategies for Backing Up and Restoring Merge Replication" in SQL Books Online.
I have the following ready to do in case of a disaster (I sure...
September 15, 2003 at 5:42 pm
There is no way to shrink the database during the restore process. The only solution is to shrink the database first and then back it up and restore it.
Gary Johnson
Microsoft...
September 15, 2003 at 5:13 pm
IMHO this is a really bad practice on a relational database. If you give people the ability to restore only one table in the database you give them the ability...
September 15, 2003 at 5:11 pm
You might try to use CREATE DATABASE ... FOR ATTACH. But basically what you really want to do is to simply restore a backup of the database. sp_Attach... only works...
September 15, 2003 at 5:02 pm
Hi gregforeman,
What language are you using to create the text box? Does the text box have a property to turn off the word wrapping of data? SQL Server couldn't care...
September 15, 2003 at 4:48 pm
I use output parameters when I KNOW that there is only going to be one value returned. Otherwise I use resultsets. There is a lot of overhead to go along...
September 15, 2003 at 4:42 pm
I haven't had any problems at all with Office XP and SQL2K.
Gary Johnson
Microsoft Natural Language Group
DBA, Sr. DB Engineer
September 15, 2003 at 4:32 pm
Many times you see the "suspect" database when the drive is too full for the database to be written to. Your solution to restore the database is the best approach...
September 12, 2003 at 4:49 pm
Try something like the following...
IF EXISTS(SELECT * FROM...)
BEGIN
put your update here
END
ELSE
BEGIN
put your insert here
END
Gary Johnson
Microsoft Natural Language Group
DBA, Sr. DB Engineer
September 12, 2003 at 4:35 pm
Can you give a little more background on what you are trying to do? Some DDL on the tables structure would really help here.
It seems to me from looking at...
September 12, 2003 at 4:32 pm
My guess is that the results coming from SQL Server are not actually in the scientic notation format you see but that either Crystal or ASP is doing the conversion...
September 12, 2003 at 4:21 pm
Viewing 15 posts - 406 through 420 (of 497 total)