Viewing 15 posts - 8,611 through 8,625 (of 22,219 total)
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
Thanks. Working on the update now.
"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:28 pm
Ah, then you're in a tough spot. Sure, HADOOP will be excellent for gathering the data (as would some of the other NoSQL solutions). But reporting, depending on the reports,...
"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:25 pm
Instead of setting Cancellation, how about AppointmentStatus. Then it's a series of things it could be, tentative, open, closed, cancelled.. other stuff. And it doesn't have to be null... 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 19, 2014 at 11:44 am
Hmmm.... I lean pretty heavily towards that proc being altered. Not arguing with you or your DBA, but that behavior is not something I've run into with sp_recompile. But, one...
"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 11:34 am
Break it down this way, most of the NoSQL solutions are awesome at collecting data, not so good at reporting from it. So, if your main focus is collection, NoSQL...
"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 11:27 am
In terms of straight data collection, many of the NoSQL options are wonderful. HADOOP would be perfect for this in terms of collecting the data. But, when it comes 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 19, 2014 at 11:19 am
Interesting question.
At first blush, I think I'd probably put the cancellation reason right in the appointment database. The reason being, why put it in a related table? It's always going...
"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 11:13 am
Viewing 15 posts - 8,611 through 8,625 (of 22,219 total)