An interesting article, but there seems to be one aspect that has not been covered.

The article suggests that there is a slight overhead using a surrogate key (as an extra...

if the initial query took 3 hours to populate 1 screen then i imagine the database developers need shooting.

i just can't conceive that there were not other solutions that did...

i can see this on every dev machine in our office as well.... how odd.

i think sql 2008 must be using the figure in "initial size" to recreate tempdb back...

further update

if you right click on any database except tempdb

then choose properties

then choose file

then the column "initial size" will tell you the current database size

but with tempdb...

update on the situation

after analysing the pattern of behaviour further it looks like the following

the file size is being incremented, but sql is not updating it's internal records.

so when tempdb...

if we shut the sql server down and re-start then tempdb is re-created - but the issue still occurs on every expand

it also applies to log files as well as...

vinodpec (4/28/2010)

---

Please explain different between the queries

SELECT *

FROM EmpAddress addr

LEFT JOIN EmpEducation edu

ON addr.empid = edu.empid

--WHERE EDU.EMPID IS NULL

WHERE addr. AddType = 2

SELECT *...

why did the servcie shut down ?

if you shut the machine down ungracefully (power cable removed) then you might have damaged master.mdf, or master.mdf has become out of log sequence...

actually you can use some of the 2008 functions even if the db is in 2000 mode

we found this when our devs started checking in 2008 code into our 2000...

it all depends on the patch - and it is not recommended in all instances

some patches are also cluster aware (in fact most these days) so you will not be...

usually someone has left a connection open to the sql server and their password has expired or their account has been disabled (or connection to the domain controller may have...

sanketahir1985 (4/9/2010)

---

Hii friends

I have one server with 4 CPU , 8GB Ram

6GB is dedicated to sql server

now we have scenario where some stored procedure get fired after every 5...

actually - i will just correct myself

you need to store the target column as text or LOB

varchar2 has a limit of 4000 byes

varchar has a length of 2000 bytes in...

you need to speak to an oracle dba on this

i'm not 100% sure on this but i beleive you need to change the target column in the oracle database to...

as far as i am aware this is correct for sql logins only

however it would be wise to check this before you accept my response as accurate

I can conformt that...