Viewing 15 posts - 28,186 through 28,200 (of 49,552 total)
You can script out logins with their passwords, you don't need to know what they are. I've seen a fair few login migration scrips, or you can use SSIS's transfer...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 6:38 am
Significant numbers of development servers?
Remember you cannot use Developer edition on a production server. It's licensed for development usage.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 6:25 am
Grant Fritchey (1/25/2011)
And remember, buy Red Gate... kidding, just kidding. Put that rock down.
Why? They give me everything for free... :w00t: :hehe:
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 6:24 am
OomBoom (1/25/2011)
The problem is not the databases it is the actual users, operators .....
p.s.Significant logins and operators on a development server?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 6:08 am
The only real difference between enterprise and developer is in the licensing. Restoring down the editions (Enterprise-standard for eg) is possible as long as enterprise-specific features haven't been used.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 6:06 am
I would strongly recommend not trying to move system databases up-version.
Script out logins (with SIDs), linked servers, operators, alerts, etc
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 5:59 am
steveb. (1/25/2011)
you could create a new database on the 2008 DE and then use SSIS to transfer all the objects across.
No need. Backup/restore works from 2005-> 2008 R2. It's...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 5:52 am
1) Don't panic
2) Don't detach the DB
3) Don't restart SQL
4) Check the SQL error log for the reason that the DB was marked suspect and plan a recovery based on...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 5:51 am
On INNER JOIN they are equivalent queries and will be executed absolutely identically. On Outer Join they are not equivalent queries and can return different results.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 5:49 am
What lead you to conclude that they are not updating automatically?
The threshold for autoupdate is 20% of the table, so you need to insert/update/delete almost 800 000 rows to trigger...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 5:47 am
HowardW (1/25/2011)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 5:33 am
scorpianprince (1/25/2011)
If huge transactions are happening and if the large insertions and deletions is a daily process then he don't have any other method.
Sure he does. Manage the log properly,...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 5:30 am
scorpianprince (1/25/2011)
Create a Job which daily shrinks your log files when the database is not in use.
No, absolutely not! Terrible practice. No file should be shrunk on a regular basis.
Step...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 5:01 am
Truncate or shrink?
Truncate marks log records as inactive and reusable and allows for space in the log to be reused. It breaks the log chain and prevents point-in-time recovery past...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 4:52 am
Autogrow isn't a maintenance plan option. It's a setting on the database files.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 4:49 am
Viewing 15 posts - 28,186 through 28,200 (of 49,552 total)