Viewing 15 posts - 6,301 through 6,315 (of 22,219 total)
Third party tool like SQL Data Compare [/url]is a great way to get something like this done.
DISCLAIMER: I work for those guys.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 15, 2015 at 11:44 am
Everything Kevin said.
Plus, if you know the queries that are giving you problems, can you look at the execution plans and, if possible, look at them prior to the upgrade....
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 15, 2015 at 11:41 am
Sounds like the default will be fine. Do you normally change the collation?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 15, 2015 at 11:37 am
SQLRNNR (4/15/2015)
Ed Wagner (4/15/2015)
BWFC (4/15/2015)
Eirikur Eiriksson (4/14/2015)
Grant Fritchey (4/14/2015)
And this makes 14,001 posts. My fingers are tired.Did you mean 0x3A99?
😎
I thought that too....Unless he posted really fast over night:-D
I figured...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 15, 2015 at 11:17 am
Also, it's really important that you don't attach massive significance to a single counter. Page Life Expectancy (PLE) is a decent measure of the behavior of some aspects of memory...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 15, 2015 at 7:27 am
No, they meant for you to use the REPLACE function in a query.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 15, 2015 at 4:36 am
You need to do this now. Run DBCC CHECKDB. Identify the objects that have allocation issues. You might get lucky. If it's a nonclustered index you can just drop and...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 15, 2015 at 4:35 am
If you schedule this to run through SQL Agent, the most common method. You can do two things, make sure that on an error it sends an email message is...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 15, 2015 at 4:22 am
What you're doing, the file utilization. Although, that's the size of the files, not the size of the data. A simple way to get a view of this is to...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 14, 2015 at 4:55 pm
Extended events filter at the point of capture. That means they radically reduce their footprint as they will only capture the events you're interested in. Trace captures every event first,...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 14, 2015 at 4:36 pm
Mind you, tracking backup size is important too, but for managing the backups and their drives, not for maintaining the database size tracking.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 14, 2015 at 12:49 pm
Fair warning, filtering in trace occurs after the trace event is captured. Filtering only really helps with the data you're storing from the capture. Extended events work much better.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 14, 2015 at 12:20 pm
I wouldn't use the backups to estimate database size. Instead I'd monitor the size and growth the database itself.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 14, 2015 at 12:19 pm
Show what you've done so far. The T-SQL syntax you're looking for is JOIN.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 14, 2015 at 11:13 am
You really shouldn't have anything in a trial environment that you're not ready to throw away. After all, the tests could have just failed.
But as others have said, export/import is...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 14, 2015 at 11:08 am
Viewing 15 posts - 6,301 through 6,315 (of 22,219 total)