Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sunsanvin
Master Smack Fu Yak Hacker
1274 Posts |
 Posted - 2008-06-24 : 02:27:58
|
| Dear All,i'm planning to drop all the non clustered indexes (as they are not congigured well) on production database, and run the latest script to create fresh non clustered indexes on specific columns. now my doubts are 1)will the replication affect with dropping and recreating of indexes?2)query to drop all the non clustered indexes on that database....can i use the query delete from sysindexes where indid>1will the query works for me to drop all the non clustered indexes?3)is it necessary to generate a snapshot again after creating the new indexes? or can i drop and run at subscriber also?please guide me in this regardArnavEven you learn 1%, Learn it with 100% confidence. |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2008-06-25 : 02:46:46
|
quote:
[i]2)query to drop all the non clustered indexes on that database....can i use the query delete from sysindexes where indid>1will the query works for me to drop all the non clustered indexes?
Not unless you want an inconsistent database with severe integrity issues and potential corruption poblems.Drop indexes using the DROP INDEX command. Never, never, never directly modify the system tables.--Gail Shaw |
 |
|
|
sunsanvin
Master Smack Fu Yak Hacker
1274 Posts |
Posted - 2008-06-25 : 03:48:30
|
| thank you gail shaw....ArnavEven you learn 1%, Learn it with 100% confidence. |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-06-25 : 12:43:38
|
| Well, If replication is running and you drop/create non-clustered indexes. You might face performance problems as it also has to replicate to Subscriber increasing your log space. |
|
|
|
|
|
|
dropping the indexes on production server