Viewing 15 posts - 14,461 through 14,475 (of 49,552 total)
Uwe Ricken (2/3/2013)
I do not understand your resentment. You can do the LAB from whatever location you want.Why do you have to travel to Europe 🙂
Bandwidth. Latency.
Imagine writing the lab...
February 3, 2013 at 8:51 am
That's a trigger, well the insert into another table part is.
For an insert to read from the client machine's registry, you will need to embed that functionality into the client...
February 3, 2013 at 7:40 am
That's not an error.
That's an informational message informing you that deleting logins does not delete the associated database users and to complete the delete you have to delete the database...
February 3, 2013 at 7:38 am
Wonderful, so not only do I have to fly to Europe when/if I need to write another lab, I need to take a laptop that can handle the Lync client...
February 3, 2013 at 7:36 am
Can't tell you which version or edition, not enough information. Review the documentation on MSDN, look at the features in each edition and version and see what you need and...
February 3, 2013 at 2:25 am
For spacial you need SQL 2008 or above (2008, 2008 R2 or 2012).
Can't tell you which version or edition, not enough information. Review the documentation on MSDN, look at the...
February 3, 2013 at 1:48 am
Please post table definitions, index definitions and execution plan, as per http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
When FORCEPLAN is set to ON, the SQL Server query optimizer processes a join in the same order as...
February 3, 2013 at 1:19 am
msocp (2/2/2013)
thanks,i just want to know must be production DB in Full Recovery. am right
Usually, but there are exceptions. Read up on what the differences are between the recovery models...
February 3, 2013 at 1:15 am
Lack of what?
Yes, low row estimation, whatever the cause, will cause very inefficient query plans. Operators that are good on smaller row counts are terrible on larger ones.
February 3, 2013 at 1:11 am
msocp (2/2/2013)
thanks,i just want to know must be production DB in Full Recovery. am right
Usually, but there are exceptions. Read up on what the differences are between the recovery models...
February 3, 2013 at 1:10 am
kramaswamy (2/2/2013)
IE, it wouldn't make sense to me to create one table called StoreTelephone, another table called StoreAddress, etc ...
Stores only ever have a single address and a single telephone...
February 2, 2013 at 12:20 pm
Well, reading all of the data pages for the table.
February 2, 2013 at 8:05 am
Take a look at the differences between the recovery models and decide based on business requirements: http://www.sqlservercentral.com/articles/Administration/75461/
February 2, 2013 at 3:33 am
begin transaction
begin try
insert ...
delete ...
commit transaction
end try
begin catch
rollback transaction
end catch
February 2, 2013 at 1:50 am
68 pages is too small to worry about. The usual threshold that's mentioned is 1000 pages. Not a hard and fast number, just a guide
February 2, 2013 at 1:39 am
Viewing 15 posts - 14,461 through 14,475 (of 49,552 total)