Viewing 15 posts - 8,611 through 8,625 (of 22,226 total)
If it's integer data, use the integer data type. Done.
Numbers in general are stored basically the same way within SQL Server. The only differences really are in the size 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
March 21, 2014 at 5:10 am
Rebuilding the log file requires that no open transactions exist in the database. Try deleting the log file and attaching the database without the log. It might not work, but...
"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
March 20, 2014 at 4:31 pm
Take a look at the estimated execution plan. It will tell you the choices SQL Server is making based on the code you provided and the statistics available on the...
"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
March 20, 2014 at 4:26 pm
Yeah, it also checks the file locations.
You need to do this:
RESTORE DATABASE MyNewDatabase
FROM DISK = 'x:\mybackupfile.bak'
WITH MOVE 'MyLogicalFileName' = 'd:\data\MyNewDatabase.mdf',
MOVE 'MyLogicalLogFileName' = 'e:\logs\MyNewDatabase.ldf';
You need to put in your appropriate paths...
"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
March 20, 2014 at 4:21 pm
It has to be either duplicate data or NULL values. With a unique index you can have a single NULL value. As was stated, with a primary key, you can't...
"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
March 20, 2014 at 4:16 pm
Rebuilding the index defragments the index, yes.
"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
March 20, 2014 at 4:13 pm
There's a bunch of stuff that's been on the deprecation list that's still not quite gone. Profiler and Trace Events are the big ones I'm curious about.
"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
March 20, 2014 at 4:10 pm
MysteryJimbo (3/20/2014)
Grant Fritchey (3/20/2014)
Further, you could set up mirroring temporarily to get the database syncronized with as little down time as possible.
This will only work if its new storage 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
March 20, 2014 at 4:40 am
paul.knibbs (3/20/2014)
Grant Fritchey (3/19/2014)So, you'd need to add the 'sa' login to the database.
I don't think you can do that, can you? 'sa' is a special login which isn't allowed...
"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
March 20, 2014 at 4:15 am
I'm also inclined towards backup and restore. It's just inherently safer than detach/attach. Further, you could set up mirroring temporarily to get the database syncronized with as little down time...
"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
March 20, 2014 at 4:14 am
Without seeing the queries and the execution plans, there's no way to suggest any indexes just based on table structure. I have no idea which column or columns are used...
"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
March 20, 2014 at 4:11 am
Virtual memory is both, the page file and your physical memory. For more on it here's the books online.
"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
March 20, 2014 at 4:06 am
Going to the source, Microsoft says not much has changed in SSIS.
"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
March 20, 2014 at 4:04 am
jeni.jm23 (3/19/2014)
Thank you. Can you explain in detail about creating a pkg and in precedure...
"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
March 20, 2014 at 3:57 am
That'll do it. Glad you figured it out.
"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
March 19, 2014 at 12:33 pm
Viewing 15 posts - 8,611 through 8,625 (of 22,226 total)