Viewing 15 posts - 481 through 495 (of 692 total)
I've been testing with it, and you're right, it seems too good to be true. BUT, with everything that I hit it with, it worked exactly as advertised!
I don't yet...
July 20, 2004 at 3:09 pm
Transactional : online transactions. The users are directly making changes to the data.
Batch updated : users don't make changes to the database. They only read it. Updates are handled by...
July 20, 2004 at 2:39 pm
Nope. If you need point in time recovery, you MUST take transaction log backups.
How many databases do you have on your server? How big? How active?
If transaction log backups...
July 20, 2004 at 2:35 pm
This should work for you. If you have a lot of users, you can create a cursor like the one I have here for the table name. Otherwise, just plug...
July 20, 2004 at 2:29 pm
This should do it.
DELETE Database2.dbo.TABLE2
FROM Database2.dbo.TABLE2 t2
INNER JOIN Database1.dbo.TABLE1 t1
ON t1.Account_number = t2.Account_number
Steve
July 20, 2004 at 2:04 pm
John,
Assuming that these are transactional databases, and that the growth is due to users' transactions:
If these are production databases, you should schedule transaction log backups frequently enough to keep the...
July 20, 2004 at 1:54 pm
You've told us that the space allocated for the db is 10GB with 2.3GB used. However, you didn't say anything about the transaction log. If the data size is 2.3GB...
July 20, 2004 at 8:51 am
You may want to take a look at the condition of your index as well, by running dbcc showcontig.
Steve
July 19, 2004 at 3:28 pm
About the only thing you can do is encrypt the data. The system administrator (sa) requires full access to all objects within SQL server to be able to do his/her...
July 19, 2004 at 1:57 pm
The differences in sizes of your transaction log backups are simply a result of heavier usage. You say that the database is used between 8am and 4pm (8 hours) and...
July 19, 2004 at 11:03 am
I stand corrected. I was thinking of stored procedures instead of tables.
I think the only way to store your procedures in SQL would be to create the tables. Are you...
July 16, 2004 at 11:47 am
If you know in advance that you'll want that information, you could run profiler. Otherwise, you would need a transaction log viewer, such as Lumigent's Log Explorer.
Steve
July 16, 2004 at 10:54 am
Shouldn't be any problem. It just can't set up dependencies if an object doesn't exist yet. Once the tables are there, it should work ok. Then, if you want to...
July 16, 2004 at 10:49 am
I'd reinstall SQL before doing a complete rebuild of the server.
Steve
July 13, 2004 at 2:16 pm
I'm kind of grasping at straws here, but have you tried running dbcc checkdb on your master and msdb databases?
Steve
July 13, 2004 at 11:34 am
Viewing 15 posts - 481 through 495 (of 692 total)