online indexing

we run maintenance nightly and in sql 2000 it would bleed into working hours and we would get trouble tickets at night of people not being able to work....

make sure all logins are created and run sp_change_users_login

tfifield (11/21/2007)

---

This is really a matter of what the database was created for. If there is only 1 front end application doing all of the inserts and deletes, there...

run a profiler session to see query performance and then make the adjustments

you will need to get with others in your IT department for this but here is what you can do

i'm guessing you don't have name resolution to the remote site....

you can also use different table names on the subscriber

we have an old legacy db from a business partner that is slowly going away with the same db/table names as...

the big part is sql 2000 to 2005. the 32 /64bit part is no biggie.

you can take databases from 64 bit and mount them on 32 bit servers and back...

steve.hindle (11/19/2007)

---

I have installed SQL 2005 but to E:\SQLServer2005 as opposed to the default installation path C:\Program Files etc. However, it still seems to have put files onto C:\? Is...

at this point there would be the dual problems of fixing the data while still running the current applications and maybe having to make up new processes because some things...

John Rowan (11/14/2007)

---

SQL Noob (11/14/2007)

---

there are no good and bad or black or white in SQL, only gray areas and what is good for your situation

we have very few FK's...

K. Brian Kelley (11/14/2007)

---

SQL Noob (11/14/2007)

---

one thing i can think they are good for is maybe reducing joins. we have queries where there is more joins than you can count...

Megha Yadav (11/15/2007)

---

Yes I do understand the importance of the foreign keys for maintaining the integrity ................but what the question is that if the system is working without it why...

one thing i can think they are good for is maybe reducing joins. we have queries where there is more joins than you can count and there is a performance...

our reporting people are notorious for creating tables with no PK's and other weird things and having queries that do 500000 reads to return 2 rows or go crazy with...

start with the execution plan