Any special way to create an index

Hi All,
I am not very experienced in creating indexes. Is there a preferred way
one should follow. I created come indexes using EM. When I do that, and
hit save on the table, does the SQL server at that point generate the
indexes?
Thanks for your comments/help.
*** Sent via Developersdex http://www.examnotes.net ***yes.
Or you can run a script from the query analyzer.
CREATE INDEX MyNewIndex ON TableName (ColumnName)
this is a very simple example. Look up "Create Index" in books on line (BOL)
for more detailed explanation
Greg Jackson
PDX, Oregon|||For what it's worth, within the Enterprise Manager's table designer, after
adding entries for your indexes, you can click the "save change script"
button instead of the "save" button, and it will display a dialog with the
SQL scripts that would be applied. You may want to save off the script, if
you are going to re-apply the indexes on other occasions.
"Vik Mohindra" <vikmohindra@.hotmail.com> wrote in message
news:Oq6yebVXFHA.2520@.TK2MSFTNGP09.phx.gbl...
> Hi All,
> I am not very experienced in creating indexes. Is there a preferred way
> one should follow. I created come indexes using EM. When I do that, and
> hit save on the table, does the SQL server at that point generate the
> indexes?
> Thanks for your comments/help.
> *** Sent via Developersdex http://www.examnotes.net ***

Any special care for CLR code when moving to other servers

I am pretty certain that once you create an assembly referring to a dll on
one server, and i decide to move that database to another server, the
assembly goes with it as part of the database and I dont have to recreate
the assembly or move the dll to the other server.. am i right ?Yes, you are right, the assembly is part of the database, even if you move
the database to another database server.
Also notice that by default on SQL Server CLR Integration is disabled so you
may need to enable it first.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Hassan" wrote:

> I am pretty certain that once you create an assembly referring to a dll on
> one server, and i decide to move that database to another server, the
> assembly goes with it as part of the database and I dont have to recreate
> the assembly or move the dll to the other server.. am i right ?
>
>

Any special care for CLR code when moving to other servers

I am pretty certain that once you create an assembly referring to a dll on
one server, and i decide to move that database to another server, the
assembly goes with it as part of the database and I dont have to recreate
the assembly or move the dll to the other server.. am i right ?Yes, you are right, the assembly is part of the database, even if you move
the database to another database server.
Also notice that by default on SQL Server CLR Integration is disabled so you
may need to enable it first.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Hassan" wrote:
> I am pretty certain that once you create an assembly referring to a dll on
> one server, and i decide to move that database to another server, the
> assembly goes with it as part of the database and I dont have to recreate
> the assembly or move the dll to the other server.. am i right ?
>
>

Any special care for CLR code when moving to other servers

I am pretty certain that once you create an assembly referring to a dll on
one server, and i decide to move that database to another server, the
assembly goes with it as part of the database and I dont have to recreate
the assembly or move the dll to the other server.. am i right ?
Yes, you are right, the assembly is part of the database, even if you move
the database to another database server.
Also notice that by default on SQL Server CLR Integration is disabled so you
may need to enable it first.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Hassan" wrote:

> I am pretty certain that once you create an assembly referring to a dll on
> one server, and i decide to move that database to another server, the
> assembly goes with it as part of the database and I dont have to recreate
> the assembly or move the dll to the other server.. am i right ?
>
>