Viewing 15 posts - 61 through 75 (of 1,065 total)
I am a leftie, and switched from using the mouse in the left hand to using it with the right hand. It took a lot of getting used to, but...
June 7, 2012 at 7:08 am
I agree with Steve... a game is always between 2 teams, so I would get rid of GameTeam and just have a foreign key to Team for HomeTeam and AwayTeam...
June 1, 2012 at 8:51 am
Hmmm... I wonder if the OP will start going for interviews as a plasterer with all this knowledge being imparted. 😛
May 28, 2012 at 6:17 am
If this is just a case of wanting to reduce the amount of typing, you can get SSMS to do most of the work for you...
If you expand a table...
May 18, 2012 at 3:40 am
I don't think you can kill the resultset, but you could do something like this...
create proc myproc
begin
select something
if exists(select somethingelse)
select somethingelse
else
select...
May 15, 2012 at 3:15 am
Just add the bit in bold...
create database dairy
on primary
(
name='address',
filename='C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\address.mdf',
size=5mb
)
log on
(
name='address_log',
filename='C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\address.ldf',
size=10mb
)
May 14, 2012 at 1:17 am
That MSDN article could certainly be made a lot less ambiguous.
On the one hand, it's true, you can't shrink a database below its original size using DBCC SHRINKDATABASE (which is...
April 16, 2012 at 1:50 am
The Select is waiting on the Insert, but, it's a deadlock... so the Insert is also waiting on the Select.
April 5, 2012 at 6:26 am
It's all pretty new to me too, but the query that has the parallel waits is the SELECT statement, so that would seem the obvious plan to do first.
April 5, 2012 at 6:09 am
This could be down to some Intra-Query parallelism.
Although your deadlock graph shows 3 processes, there are only 2 spids involved, and one of the waits involves a parallel exchange...
April 5, 2012 at 5:05 am
Agreed... it looks like our reading of the original requirement is different.
I assumed the test would involve a role switch and back again, but with some updates done at the...
March 27, 2012 at 2:57 am
GilaMonster (3/27/2012)
Since you're bringing the secondary DB online and making changes, there's no 'go back' after that.
Are you sure? This was something I had done previously (SQL2000 admittedly) with...
March 27, 2012 at 2:26 am
You mention problems when there is a large update on the publisher. Is there any way you can reduce the size of the update transactions there (i.e. more transactions, but...
March 27, 2012 at 2:17 am
You won't break log shipping... have a look in BOL at Log Shipping Role Changes.
Essentially, you do your final transaction log backup at the primary using "WITH NORECOVERY", then
restore...
March 27, 2012 at 1:39 am
Viewing 15 posts - 61 through 75 (of 1,065 total)