Viewing 15 posts - 286 through 300 (of 1,068 total)
1) If you don't need point-in-time restore, you can keep the database in SIMPLE recovery model.
2) If log files get to max SIZE, database becomes read-only. That is, only...
March 13, 2012 at 10:19 pm
MSQLDBA (3/13/2012)
After running your script result:DBNAMEDBIDTotal Size in MBAvailable Space In MB
TEST1040
and run sp_spaceused command result,
database_namedatabase_sizeunallocated space
TEST6.44 MB0.38 MB
Is this database originally from SQL 2000 version? If you run DBCC...
March 13, 2012 at 9:59 am
Shodhan,
There are couple of issues with the solutions mentioned by you.
1) BACKUP LOG WITH TRUNCATE_ONLY removes the log entries from log file. So point-in-time restore is not possible. (btw this...
March 13, 2012 at 3:51 am
Best practice:
1) Pre-size the file.
2) Avoid auto-growth by manually pre-sizing the file required size.
3) Avoid file shrinking.
4) Take log-backup regularly by creating a maintenance plan or job
5) Create an...
March 13, 2012 at 2:00 am
Transaction log backup truncates the log entries, but does not shrink the log file.
You need to shrink the file manually.
Yes, it should be safer.
March 12, 2012 at 11:50 pm
There is NO "transactions folder" in replication. There is what is called "snapshot folder".
Please do read the book "How to become an exceptional DBA" by Brad McGehee available here.
March 12, 2012 at 10:38 pm
Try this:
execute sp_replicationdboption 'dbname','Publish','False',1
March 12, 2012 at 9:57 am
Use this query:
SELECT
DB_NAME() As DBNAME
, DB_ID() AS DBID
, SUM(size / 128) AS 'Total Size in MB'
, SUM(size / 128 -...
March 11, 2012 at 10:35 am
Run DBCC CHECKDB(dbname) WITH NO_INFOMSGS and post the output here.
DON'T detach the db. Don't restart the service or server.
March 11, 2012 at 10:23 am
Is Auto-Shrinkk ON?
May be silly question. Still better to confirm.
March 10, 2012 at 8:53 am
Guras (3/8/2012)
Database1data file 11432 87992633...
March 8, 2012 at 10:26 pm
Grant Fritchey has written a nice book on interpreting query plan.
Please download and read it. It is free:
March 8, 2012 at 9:01 pm
Inserting row by row is certainly not efficient.
Have you tried BCP? It is the most efficient tools for inserting large number of rows into SQL Server.
You can sort out the...
March 8, 2012 at 10:42 am
uniqueidentifier is a data type.
BOL
Merge replication and transactional replication with updating subscriptions use uniqueidentifier columns to guarantee that rows are uniquely identified across multiple copies of the table.
March 8, 2012 at 10:33 am
By "on the fly no intermediary csv file" do you mean directly from the source to SQL Server?
What is the source?
Import/Export wizard or SSIS may be the suitable tool for...
March 8, 2012 at 10:24 am
Viewing 15 posts - 286 through 300 (of 1,068 total)