Viewing 15 posts - 2,641 through 2,655 (of 2,904 total)
Also check out this...
http://www.sqlservercentral.com/columnists/rsharma/copydatabase.asp
It's a pretty good article and part way through it talks about moving logins from one server to another.
-SQLBill
July 7, 2003 at 11:31 am
I haven't seen it before, but I'm guessing that the Service Pack puts the databases in single user mode 'behind the scenes'. That way it can upgrade without being interfered...
July 7, 2003 at 11:27 am
The TEMPDB is not automatically truncated. You can truncate it by stopping and restarting the services.
I believe this is a 'feature' of MS SQL Server. Look at it this...
July 7, 2003 at 11:24 am
I just placed my order. I'm looking forward to the book coming out and I hope it's a great success for all of you.
-SQLBill
July 7, 2003 at 8:21 am
As MarkusB showed you, just convert one of the numbers to a decimal and your problem will be solved. But if you can't just add the zero you can try...
July 7, 2003 at 8:09 am
One possibility:
You have a user that is dropping and recreating their database on a daily basis.
Why do I think this?
The TEMPDB is used to keep track of changes to databases...
July 7, 2003 at 8:05 am
guarddata,
Thanks. I wasn't aware (and didn't think to try it) that converting only one part would also work.
I learned something new today.
-SQLBill
July 3, 2003 at 12:21 pm
To work properly, the integers must have be converted to decimals first.
Try these three scripts:
select convert(decimal(5,2), 10/3)
and
select convert(decimal(5,2), 10.0/3.0)
and
select convert(decimal(3,2), (convert(decimal(3,1),10)/convert(decimal(3,1),3)))
The second script requires YOU to manually add the decimal...
July 3, 2003 at 11:47 am
If your TEMPDB log is filling up, then yes you need to increase the amount it grows by.
However, you might want to consider setting it to grow by MB instead...
July 3, 2003 at 7:54 am
The select into/bulk copy option is mainly to make bulk inserts/updates go smoothly. When doing a huge insert, the transaction log needs to continuously grow and it might not be...
July 3, 2003 at 7:48 am
I don't think it's a problem with Enterprise Manager. I think the user doesn't have permission to access the tape device.
Also, PLEASE upgrade to Service Pack 3 immediately. You are...
July 2, 2003 at 10:13 am
What does the VARCHAR data look like? BIGINT does not allow decimals.
SQL's TIMESTAMP is really used to 'version stamp table rows'. Read up on this in the Books Online (BOL).
If...
July 2, 2003 at 10:10 am
Since you don't have the .ldf file (log file), you will have to use the procedure:
sp_attach_single_db_file
See the Books OnLine for more information on the usage and syntax.
-SQLBill
July 2, 2003 at 10:04 am
As jpipes stated, that error means there are two or more possible columns with that name and you need to identify which one the query is to use.
Specifically, you have:
CASE30.Sender
CASEOLDR.Sender
Two...
July 2, 2003 at 10:03 am
TEMPDB can fill up and lock users/queries if you don't have it set to automatically grow enough. Notice I said 'enough'. The growth size has to be enough that it...
July 2, 2003 at 9:55 am
Viewing 15 posts - 2,641 through 2,655 (of 2,904 total)