Do you have the process that you are looking at as it might give people some pointers as to why this is happening.

with my limited knowledge tempdb is used...

I don't believe that the original size is stored anywhere only the current size.

I have seen Access Forms running over the top of SQL server, it works but its far from ideal.

Is the intention to port the Access application directly to SQL server?...

darrylc-ssc (4/3/2013)

---

There are other more sophisticated ways to do this but here is a quickie example given a simple Policy table such as you describe and requiring no dates to...

It might be worth splitting out the derived tables into temp tables then use them to form part of the delete this should reduce the amount of blocking that's going...

I believe that MS have stated that all hints will require the WITH statement in future to make it consistent.

You shouldn't be using the WITH (NOLOCK) hint It can have...

Unfortunately there is no magic wand to do this, so its a pain staking trawl through all SP's, as people may have used Aliases, etc.

You might be able to...

Kapil,

Its a setting on the Instance.

1) Open SSMS and connect to Instance

2) right click on Instance name and select properties

3) Select Memory item

4) Look at the Max Server Memory...

No you don't need to restart SQL server if you change the Max Server Memory setting it should automatically adjust to the new level.

Out of curiosity did you increase...

Thanks Sean, as for pain, I don't think you understand the meaning, the ETL I'm breaking apart runs in 7 hours, the largest dim is about 200 columns wide, and...

jbalbo (3/27/2013)

---

Tried this below with no luck

I Wanted to use today's date if the parameter @enddate was greater than today

WHERE (KindOfDay = 'Weekday') AND (Date BETWEEN...

Trust me the project is insanity personified.

you could populate a 50 column table with 100,000 rows all with GUIDS, then Cross join to itself and if that doesn't work add an Order by, for a good...

Or you could just do

SET @sql = 'SELECT * FROM '+QuoteName(@C1_Name) + '..[MyTable]'

PRINT @sql

EXEC (@SQL)

Normally you reorganise the index if the fragmentation is less than 30% (I think MS recommends a 20% threshold) over that and you start to look at rebuilding the index...