Joining a domain

One of our SQL servers is not joined to the company domain. We don't know wh
y
the previous IT persons didn't join it to the domain. We're thinking to join
it to the domain now. Is there going to be a problem with that?
Thanks.Hi
There should not be any problem. If you normally use domain accounts for the
services they will probably need to be change. If you change the server name
then you will need to follow
http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
Server.
John
"lwidjaya" wrote:

> One of our SQL servers is not joined to the company domain. We don't know
why
> the previous IT persons didn't join it to the domain. We're thinking to jo
in
> it to the domain now. Is there going to be a problem with that?
> Thanks.|||Thanks for your answer. Another thing. We have another SQL server for our ER
P
system and we're going to set up a new server with a new name replacing this
server. We have a number of views linked to a database in the old server. Is
there an easy way to update all views with the new server name?
Thanks.
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> There should not be any problem. If you normally use domain accounts for t
he
> services they will probably need to be change. If you change the server na
me
> then you will need to follow
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> Server.
> John
> "lwidjaya" wrote:
>|||Hi Lisa
If your new server has a different name, you would have to create a new
linked server and drop the old one. The views can be scripted and the server
name replaced using an editor; the script(s) can then be run to re-create th
e
views (assuming they are not encrypted views!). You would not need to do the
scripting if you had you the view definitions in source code control.
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Thanks for your answer. Another thing. We have another SQL server for our
ERP
> system and we're going to set up a new server with a new name replacing th
is
> server. We have a number of views linked to a database in the old server.
Is
> there an easy way to update all views with the new server name?
> Thanks.
>
> "John Bell" wrote:
>|||Hi John:
I'm not good in DBA. Could you tell me how to script the views and run it? I
don't think the views are encrypted.
Thanks a lot,
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> If your new server has a different name, you would have to create a new
> linked server and drop the old one. The views can be scripted and the serv
er
> name replaced using an editor; the script(s) can then be run to re-create
the
> views (assuming they are not encrypted views!). You would not need to do t
he
> scripting if you had you the view definitions in source code control.
> John
> "lwidjaya" wrote:
>|||Hi Lisa
The easiest way is to use Enterprise Manager, this assumes you have already
registered the database server.
1. Start Enterprise Manager
2. Open up the tree view so you can see the database you are wishing to
script (Under databases)
3. Right Click the database name and choose All Tasks/Generate SQL Script
4. You will Generate SQL Script dialog. Press the Show All button
5. Choose the All views check box. This will list all the views in the
Objects to be Scripted list box.
6. On the options tab, choose Windows Text (Ansi)
7. Press the OK button, this will prompt you for a file name.
You can then open this file in Query analyser and make the changes needed to
the linked server name.
You don't actually need to change these views if you dropped the existing
linked server and the created the linked server that points to the new
server, but still have the same linked server name as the old server. This
may lead to confusion though!!
HTH
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Hi John:
> I'm not good in DBA. Could you tell me how to script the views and run it?
I
> don't think the views are encrypted.
> Thanks a lot,
> Lisa
> "John Bell" wrote:
>|||Hi John,
thanks for your reply.
So, after I created the script and made the changes, I can just run the
script, right?
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> The easiest way is to use Enterprise Manager, this assumes you have alread
y
> registered the database server.
> 1. Start Enterprise Manager
> 2. Open up the tree view so you can see the database you are wishing to
> script (Under databases)
> 3. Right Click the database name and choose All Tasks/Generate SQL Script
> 4. You will Generate SQL Script dialog. Press the Show All button
> 5. Choose the All views check box. This will list all the views in the
> Objects to be Scripted list box.
> 6. On the options tab, choose Windows Text (Ansi)
> 7. Press the OK button, this will prompt you for a file name.
> You can then open this file in Query analyser and make the changes needed
to
> the linked server name.
> You don't actually need to change these views if you dropped the existing
> linked server and the created the linked server that points to the new
> server, but still have the same linked server name as the old server. This
> may lead to confusion though!!
> HTH
> John
>
> "lwidjaya" wrote:
>|||Hi Lisa
If you have created the linked server, then running the script to drop and
recreate the views in Query analyser should mean you are then using the new
server. Make sure that all the permissions are correct. You may want to do a
test run on a backup//different system before moving the live database.
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Hi John,
> thanks for your reply.
> So, after I created the script and made the changes, I can just run the
> script, right?
> Lisa
> "John Bell" wrote:
>|||Thanks a lot, John!
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> If you have created the linked server, then running the script to drop and
> recreate the views in Query analyser should mean you are then using the ne
w
> server. Make sure that all the permissions are correct. You may want to do
a
> test run on a backup//different system before moving the live database.
> John
> "lwidjaya" wrote:
>

Joining a domain

One of our SQL servers is not joined to the company domain. We don't know why
the previous IT persons didn't join it to the domain. We're thinking to join
it to the domain now. Is there going to be a problem with that?
Thanks.Hi
There should not be any problem. If you normally use domain accounts for the
services they will probably need to be change. If you change the server name
then you will need to follow
http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
Server.
John
"lwidjaya" wrote:
> One of our SQL servers is not joined to the company domain. We don't know why
> the previous IT persons didn't join it to the domain. We're thinking to join
> it to the domain now. Is there going to be a problem with that?
> Thanks.|||Thanks for your answer. Another thing. We have another SQL server for our ERP
system and we're going to set up a new server with a new name replacing this
server. We have a number of views linked to a database in the old server. Is
there an easy way to update all views with the new server name?
Thanks.
Lisa
"John Bell" wrote:
> Hi
> There should not be any problem. If you normally use domain accounts for the
> services they will probably need to be change. If you change the server name
> then you will need to follow
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> Server.
> John
> "lwidjaya" wrote:
> > One of our SQL servers is not joined to the company domain. We don't know why
> > the previous IT persons didn't join it to the domain. We're thinking to join
> > it to the domain now. Is there going to be a problem with that?
> > Thanks.|||Hi Lisa
If your new server has a different name, you would have to create a new
linked server and drop the old one. The views can be scripted and the server
name replaced using an editor; the script(s) can then be run to re-create the
views (assuming they are not encrypted views!). You would not need to do the
scripting if you had you the view definitions in source code control.
John
"lwidjaya" wrote:
> Thanks for your answer. Another thing. We have another SQL server for our ERP
> system and we're going to set up a new server with a new name replacing this
> server. We have a number of views linked to a database in the old server. Is
> there an easy way to update all views with the new server name?
> Thanks.
>
> "John Bell" wrote:
> > Hi
> >
> > There should not be any problem. If you normally use domain accounts for the
> > services they will probably need to be change. If you change the server name
> > then you will need to follow
> > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > Server.
> >
> > John
> >
> > "lwidjaya" wrote:
> >
> > > One of our SQL servers is not joined to the company domain. We don't know why
> > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > it to the domain now. Is there going to be a problem with that?
> > > Thanks.|||Hi John:
I'm not good in DBA. Could you tell me how to script the views and run it? I
don't think the views are encrypted.
Thanks a lot,
Lisa
"John Bell" wrote:
> Hi Lisa
> If your new server has a different name, you would have to create a new
> linked server and drop the old one. The views can be scripted and the server
> name replaced using an editor; the script(s) can then be run to re-create the
> views (assuming they are not encrypted views!). You would not need to do the
> scripting if you had you the view definitions in source code control.
> John
> "lwidjaya" wrote:
> > Thanks for your answer. Another thing. We have another SQL server for our ERP
> > system and we're going to set up a new server with a new name replacing this
> > server. We have a number of views linked to a database in the old server. Is
> > there an easy way to update all views with the new server name?
> >
> > Thanks.
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > There should not be any problem. If you normally use domain accounts for the
> > > services they will probably need to be change. If you change the server name
> > > then you will need to follow
> > > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > > Server.
> > >
> > > John
> > >
> > > "lwidjaya" wrote:
> > >
> > > > One of our SQL servers is not joined to the company domain. We don't know why
> > > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > > it to the domain now. Is there going to be a problem with that?
> > > > Thanks.|||Hi Lisa
The easiest way is to use Enterprise Manager, this assumes you have already
registered the database server.
1. Start Enterprise Manager
2. Open up the tree view so you can see the database you are wishing to
script (Under databases)
3. Right Click the database name and choose All Tasks/Generate SQL Script
4. You will Generate SQL Script dialog. Press the Show All button
5. Choose the All views check box. This will list all the views in the
Objects to be Scripted list box.
6. On the options tab, choose Windows Text (Ansi)
7. Press the OK button, this will prompt you for a file name.
You can then open this file in Query analyser and make the changes needed to
the linked server name.
You don't actually need to change these views if you dropped the existing
linked server and the created the linked server that points to the new
server, but still have the same linked server name as the old server. This
may lead to confusion though!!
HTH
John
"lwidjaya" wrote:
> Hi John:
> I'm not good in DBA. Could you tell me how to script the views and run it? I
> don't think the views are encrypted.
> Thanks a lot,
> Lisa
> "John Bell" wrote:
> > Hi Lisa
> >
> > If your new server has a different name, you would have to create a new
> > linked server and drop the old one. The views can be scripted and the server
> > name replaced using an editor; the script(s) can then be run to re-create the
> > views (assuming they are not encrypted views!). You would not need to do the
> > scripting if you had you the view definitions in source code control.
> >
> > John
> >
> > "lwidjaya" wrote:
> >
> > > Thanks for your answer. Another thing. We have another SQL server for our ERP
> > > system and we're going to set up a new server with a new name replacing this
> > > server. We have a number of views linked to a database in the old server. Is
> > > there an easy way to update all views with the new server name?
> > >
> > > Thanks.
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > There should not be any problem. If you normally use domain accounts for the
> > > > services they will probably need to be change. If you change the server name
> > > > then you will need to follow
> > > > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > > > Server.
> > > >
> > > > John
> > > >
> > > > "lwidjaya" wrote:
> > > >
> > > > > One of our SQL servers is not joined to the company domain. We don't know why
> > > > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > > > it to the domain now. Is there going to be a problem with that?
> > > > > Thanks.|||Hi John,
thanks for your reply.
So, after I created the script and made the changes, I can just run the
script, right?
Lisa
"John Bell" wrote:
> Hi Lisa
> The easiest way is to use Enterprise Manager, this assumes you have already
> registered the database server.
> 1. Start Enterprise Manager
> 2. Open up the tree view so you can see the database you are wishing to
> script (Under databases)
> 3. Right Click the database name and choose All Tasks/Generate SQL Script
> 4. You will Generate SQL Script dialog. Press the Show All button
> 5. Choose the All views check box. This will list all the views in the
> Objects to be Scripted list box.
> 6. On the options tab, choose Windows Text (Ansi)
> 7. Press the OK button, this will prompt you for a file name.
> You can then open this file in Query analyser and make the changes needed to
> the linked server name.
> You don't actually need to change these views if you dropped the existing
> linked server and the created the linked server that points to the new
> server, but still have the same linked server name as the old server. This
> may lead to confusion though!!
> HTH
> John
>
> "lwidjaya" wrote:
> > Hi John:
> > I'm not good in DBA. Could you tell me how to script the views and run it? I
> > don't think the views are encrypted.
> >
> > Thanks a lot,
> >
> > Lisa
> >
> > "John Bell" wrote:
> >
> > > Hi Lisa
> > >
> > > If your new server has a different name, you would have to create a new
> > > linked server and drop the old one. The views can be scripted and the server
> > > name replaced using an editor; the script(s) can then be run to re-create the
> > > views (assuming they are not encrypted views!). You would not need to do the
> > > scripting if you had you the view definitions in source code control.
> > >
> > > John
> > >
> > > "lwidjaya" wrote:
> > >
> > > > Thanks for your answer. Another thing. We have another SQL server for our ERP
> > > > system and we're going to set up a new server with a new name replacing this
> > > > server. We have a number of views linked to a database in the old server. Is
> > > > there an easy way to update all views with the new server name?
> > > >
> > > > Thanks.
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > There should not be any problem. If you normally use domain accounts for the
> > > > > services they will probably need to be change. If you change the server name
> > > > > then you will need to follow
> > > > > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > > > > Server.
> > > > >
> > > > > John
> > > > >
> > > > > "lwidjaya" wrote:
> > > > >
> > > > > > One of our SQL servers is not joined to the company domain. We don't know why
> > > > > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > > > > it to the domain now. Is there going to be a problem with that?
> > > > > > Thanks.|||Hi Lisa
If you have created the linked server, then running the script to drop and
recreate the views in Query analyser should mean you are then using the new
server. Make sure that all the permissions are correct. You may want to do a
test run on a backup//different system before moving the live database.
John
"lwidjaya" wrote:
> Hi John,
> thanks for your reply.
> So, after I created the script and made the changes, I can just run the
> script, right?
> Lisa
> "John Bell" wrote:
> > Hi Lisa
> >
> > The easiest way is to use Enterprise Manager, this assumes you have already
> > registered the database server.
> >
> > 1. Start Enterprise Manager
> > 2. Open up the tree view so you can see the database you are wishing to
> > script (Under databases)
> > 3. Right Click the database name and choose All Tasks/Generate SQL Script
> > 4. You will Generate SQL Script dialog. Press the Show All button
> > 5. Choose the All views check box. This will list all the views in the
> > Objects to be Scripted list box.
> > 6. On the options tab, choose Windows Text (Ansi)
> > 7. Press the OK button, this will prompt you for a file name.
> >
> > You can then open this file in Query analyser and make the changes needed to
> > the linked server name.
> >
> > You don't actually need to change these views if you dropped the existing
> > linked server and the created the linked server that points to the new
> > server, but still have the same linked server name as the old server. This
> > may lead to confusion though!!
> >
> > HTH
> >
> > John
> >
> >
> >
> > "lwidjaya" wrote:
> >
> > > Hi John:
> > > I'm not good in DBA. Could you tell me how to script the views and run it? I
> > > don't think the views are encrypted.
> > >
> > > Thanks a lot,
> > >
> > > Lisa
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi Lisa
> > > >
> > > > If your new server has a different name, you would have to create a new
> > > > linked server and drop the old one. The views can be scripted and the server
> > > > name replaced using an editor; the script(s) can then be run to re-create the
> > > > views (assuming they are not encrypted views!). You would not need to do the
> > > > scripting if you had you the view definitions in source code control.
> > > >
> > > > John
> > > >
> > > > "lwidjaya" wrote:
> > > >
> > > > > Thanks for your answer. Another thing. We have another SQL server for our ERP
> > > > > system and we're going to set up a new server with a new name replacing this
> > > > > server. We have a number of views linked to a database in the old server. Is
> > > > > there an easy way to update all views with the new server name?
> > > > >
> > > > > Thanks.
> > > > >
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > There should not be any problem. If you normally use domain accounts for the
> > > > > > services they will probably need to be change. If you change the server name
> > > > > > then you will need to follow
> > > > > > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > > > > > Server.
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "lwidjaya" wrote:
> > > > > >
> > > > > > > One of our SQL servers is not joined to the company domain. We don't know why
> > > > > > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > > > > > it to the domain now. Is there going to be a problem with that?
> > > > > > > Thanks.|||Thanks a lot, John!
"John Bell" wrote:
> Hi Lisa
> If you have created the linked server, then running the script to drop and
> recreate the views in Query analyser should mean you are then using the new
> server. Make sure that all the permissions are correct. You may want to do a
> test run on a backup//different system before moving the live database.
> John
> "lwidjaya" wrote:
> > Hi John,
> > thanks for your reply.
> > So, after I created the script and made the changes, I can just run the
> > script, right?
> >
> > Lisa
> >
> > "John Bell" wrote:
> >
> > > Hi Lisa
> > >
> > > The easiest way is to use Enterprise Manager, this assumes you have already
> > > registered the database server.
> > >
> > > 1. Start Enterprise Manager
> > > 2. Open up the tree view so you can see the database you are wishing to
> > > script (Under databases)
> > > 3. Right Click the database name and choose All Tasks/Generate SQL Script
> > > 4. You will Generate SQL Script dialog. Press the Show All button
> > > 5. Choose the All views check box. This will list all the views in the
> > > Objects to be Scripted list box.
> > > 6. On the options tab, choose Windows Text (Ansi)
> > > 7. Press the OK button, this will prompt you for a file name.
> > >
> > > You can then open this file in Query analyser and make the changes needed to
> > > the linked server name.
> > >
> > > You don't actually need to change these views if you dropped the existing
> > > linked server and the created the linked server that points to the new
> > > server, but still have the same linked server name as the old server. This
> > > may lead to confusion though!!
> > >
> > > HTH
> > >
> > > John
> > >
> > >
> > >
> > > "lwidjaya" wrote:
> > >
> > > > Hi John:
> > > > I'm not good in DBA. Could you tell me how to script the views and run it? I
> > > > don't think the views are encrypted.
> > > >
> > > > Thanks a lot,
> > > >
> > > > Lisa
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi Lisa
> > > > >
> > > > > If your new server has a different name, you would have to create a new
> > > > > linked server and drop the old one. The views can be scripted and the server
> > > > > name replaced using an editor; the script(s) can then be run to re-create the
> > > > > views (assuming they are not encrypted views!). You would not need to do the
> > > > > scripting if you had you the view definitions in source code control.
> > > > >
> > > > > John
> > > > >
> > > > > "lwidjaya" wrote:
> > > > >
> > > > > > Thanks for your answer. Another thing. We have another SQL server for our ERP
> > > > > > system and we're going to set up a new server with a new name replacing this
> > > > > > server. We have a number of views linked to a database in the old server. Is
> > > > > > there an easy way to update all views with the new server name?
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > >
> > > > > > "John Bell" wrote:
> > > > > >
> > > > > > > Hi
> > > > > > >
> > > > > > > There should not be any problem. If you normally use domain accounts for the
> > > > > > > services they will probably need to be change. If you change the server name
> > > > > > > then you will need to follow
> > > > > > > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > > > > > > Server.
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > > "lwidjaya" wrote:
> > > > > > >
> > > > > > > > One of our SQL servers is not joined to the company domain. We don't know why
> > > > > > > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > > > > > > it to the domain now. Is there going to be a problem with that?
> > > > > > > > Thanks.

Joining a domain

One of our SQL servers is not joined to the company domain. We don't know why
the previous IT persons didn't join it to the domain. We're thinking to join
it to the domain now. Is there going to be a problem with that?
Thanks.
Hi
There should not be any problem. If you normally use domain accounts for the
services they will probably need to be change. If you change the server name
then you will need to follow
http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
Server.
John
"lwidjaya" wrote:

> One of our SQL servers is not joined to the company domain. We don't know why
> the previous IT persons didn't join it to the domain. We're thinking to join
> it to the domain now. Is there going to be a problem with that?
> Thanks.
|||Thanks for your answer. Another thing. We have another SQL server for our ERP
system and we're going to set up a new server with a new name replacing this
server. We have a number of views linked to a database in the old server. Is
there an easy way to update all views with the new server name?
Thanks.
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> There should not be any problem. If you normally use domain accounts for the
> services they will probably need to be change. If you change the server name
> then you will need to follow
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> Server.
> John
> "lwidjaya" wrote:
|||Hi Lisa
If your new server has a different name, you would have to create a new
linked server and drop the old one. The views can be scripted and the server
name replaced using an editor; the script(s) can then be run to re-create the
views (assuming they are not encrypted views!). You would not need to do the
scripting if you had you the view definitions in source code control.
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Thanks for your answer. Another thing. We have another SQL server for our ERP
> system and we're going to set up a new server with a new name replacing this
> server. We have a number of views linked to a database in the old server. Is
> there an easy way to update all views with the new server name?
> Thanks.
>
> "John Bell" wrote:
|||Hi John:
I'm not good in DBA. Could you tell me how to script the views and run it? I
don't think the views are encrypted.
Thanks a lot,
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> If your new server has a different name, you would have to create a new
> linked server and drop the old one. The views can be scripted and the server
> name replaced using an editor; the script(s) can then be run to re-create the
> views (assuming they are not encrypted views!). You would not need to do the
> scripting if you had you the view definitions in source code control.
> John
> "lwidjaya" wrote:
|||Hi Lisa
The easiest way is to use Enterprise Manager, this assumes you have already
registered the database server.
1. Start Enterprise Manager
2. Open up the tree view so you can see the database you are wishing to
script (Under databases)
3. Right Click the database name and choose All Tasks/Generate SQL Script
4. You will Generate SQL Script dialog. Press the Show All button
5. Choose the All views check box. This will list all the views in the
Objects to be Scripted list box.
6. On the options tab, choose Windows Text (Ansi)
7. Press the OK button, this will prompt you for a file name.
You can then open this file in Query analyser and make the changes needed to
the linked server name.
You don't actually need to change these views if you dropped the existing
linked server and the created the linked server that points to the new
server, but still have the same linked server name as the old server. This
may lead to confusion though!!
HTH
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Hi John:
> I'm not good in DBA. Could you tell me how to script the views and run it? I
> don't think the views are encrypted.
> Thanks a lot,
> Lisa
> "John Bell" wrote:
|||Hi John,
thanks for your reply.
So, after I created the script and made the changes, I can just run the
script, right?
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> The easiest way is to use Enterprise Manager, this assumes you have already
> registered the database server.
> 1. Start Enterprise Manager
> 2. Open up the tree view so you can see the database you are wishing to
> script (Under databases)
> 3. Right Click the database name and choose All Tasks/Generate SQL Script
> 4. You will Generate SQL Script dialog. Press the Show All button
> 5. Choose the All views check box. This will list all the views in the
> Objects to be Scripted list box.
> 6. On the options tab, choose Windows Text (Ansi)
> 7. Press the OK button, this will prompt you for a file name.
> You can then open this file in Query analyser and make the changes needed to
> the linked server name.
> You don't actually need to change these views if you dropped the existing
> linked server and the created the linked server that points to the new
> server, but still have the same linked server name as the old server. This
> may lead to confusion though!!
> HTH
> John
>
> "lwidjaya" wrote:
|||Hi Lisa
If you have created the linked server, then running the script to drop and
recreate the views in Query analyser should mean you are then using the new
server. Make sure that all the permissions are correct. You may want to do a
test run on a backup//different system before moving the live database.
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Hi John,
> thanks for your reply.
> So, after I created the script and made the changes, I can just run the
> script, right?
> Lisa
> "John Bell" wrote:
|||Thanks a lot, John!
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> If you have created the linked server, then running the script to drop and
> recreate the views in Query analyser should mean you are then using the new
> server. Make sure that all the permissions are correct. You may want to do a
> test run on a backup//different system before moving the live database.
> John
> "lwidjaya" wrote:

Join the Result of xp_logininfo with a table

Hello group!

i have a table "group_code" wich relates the names of
nt-(domain)-groups to codes. now i want use the stored procedure
xp_logininfo (asking for the group-membership of the current user) to
join the result to "group_code". then i must use the new result (the
code) to join against other tables.

i know now, that i cant join results of SPs against tables. may be that
a UDF with a table result is the correct approach. but i have no idea
how to wrap the xp_logininfo in a UDF.

a other way can be to do in a UDF the same thing like the xp_logininfo.
then this UDF should deliver at least the nt-(domain)-groups in wich
the current-user is a member.

Is there anybody who can give me the code for that?
many thanx in advance.

Karl(Karl.Auer@.gmail.com) writes:
> i have a table "group_code" wich relates the names of
> nt-(domain)-groups to codes. now i want use the stored procedure
> xp_logininfo (asking for the group-membership of the current user) to
> join the result to "group_code". then i must use the new result (the
> code) to join against other tables.
> i know now, that i cant join results of SPs against tables. may be that
> a UDF with a table result is the correct approach. but i have no idea
> how to wrap the xp_logininfo in a UDF.
> a other way can be to do in a UDF the same thing like the xp_logininfo.
> then this UDF should deliver at least the nt-(domain)-groups in wich
> the current-user is a member.

I don't think you can do this with a UDF. You can do:

CREATE TABLE #temp (...)
INSERT #temp (...)
EXEC master..xp_logininfo

But you cannot do this in a UDF, since you cannot create temp
tables in a UDF, and you cannot do INSERT EXEC on a table variable
if memory serves.

As for how #temp in the example should be created, see the definition
of the columns for xp_logininfo in Books Online.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

join SQL server into domain

Hi all,
I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
backend database server; one Sharepoint server; one SQL Report Server web
server.
I'm going to join these 3 servers into AD domain, will it cause any problem?
Will it break the connection between the SQL server and the other 2 servers?
Anyone has experience on this? Thanks!
MliHi
If you rename the server then you will need to
http://msdn2.microsoft.com/en-us/library/ms143799.aspx and also change any
connections strings to the new name. Logins from the old workgroup may need
removing and new ones added for the domain. Service accounts may require
changing and orphaned users may need to be resolved
http://support.microsoft.com/kb/314546. If you create any new users they wil
l
need to have permissions added.
John
"MLi" wrote:

> Hi all,
> I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
> backend database server; one Sharepoint server; one SQL Report Server web
> server.
> I'm going to join these 3 servers into AD domain, will it cause any proble
m?
> Will it break the connection between the SQL server and the other 2 server
s?
> Anyone has experience on this? Thanks!
>
> Mli
>
>
>|||Thanks John.
I'm not gonna change the server name, however because it will be joined a
domain, the DNS name will be changed. Is there any concern?
MLi
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:26F04787-0DB9-4C8C-8D60-1EA65E52F8E7@.microsoft.com...[vbcol=seagreen]
> Hi
> If you rename the server then you will need to
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx and also change any
> connections strings to the new name. Logins from the old workgroup may
> need
> removing and new ones added for the domain. Service accounts may require
> changing and orphaned users may need to be resolved
> http://support.microsoft.com/kb/314546. If you create any new users they
> will
> need to have permissions added.
> John
> "MLi" wrote:
>|||Hi
The name of the instance will still be the name of the old servername,
SELECT @.@.SERVERNAME will still show the old one. That is why you need to dro
p
it and create the new one.
John
"MLi" wrote:

> Thanks John.
> I'm not gonna change the server name, however because it will be joined a
> domain, the DNS name will be changed. Is there any concern?
>
> MLi
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:26F04787-0DB9-4C8C-8D60-1EA65E52F8E7@.microsoft.com...
>
>

join SQL server into domain

Hi all,
I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
backend database server; one Sharepoint server; one SQL Report Server web
server.
I'm going to join these 3 servers into AD domain, will it cause any problem?
Will it break the connection between the SQL server and the other 2 servers?
Anyone has experience on this? Thanks!
MliHi
If you rename the server then you will need to
http://msdn2.microsoft.com/en-us/library/ms143799.aspx and also change any
connections strings to the new name. Logins from the old workgroup may need
removing and new ones added for the domain. Service accounts may require
changing and orphaned users may need to be resolved
http://support.microsoft.com/kb/314546. If you create any new users they will
need to have permissions added.
John
"MLi" wrote:
> Hi all,
> I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
> backend database server; one Sharepoint server; one SQL Report Server web
> server.
> I'm going to join these 3 servers into AD domain, will it cause any problem?
> Will it break the connection between the SQL server and the other 2 servers?
> Anyone has experience on this? Thanks!
>
> Mli
>
>
>|||Thanks John.
I'm not gonna change the server name, however because it will be joined a
domain, the DNS name will be changed. Is there any concern?
MLi
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:26F04787-0DB9-4C8C-8D60-1EA65E52F8E7@.microsoft.com...
> Hi
> If you rename the server then you will need to
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx and also change any
> connections strings to the new name. Logins from the old workgroup may
> need
> removing and new ones added for the domain. Service accounts may require
> changing and orphaned users may need to be resolved
> http://support.microsoft.com/kb/314546. If you create any new users they
> will
> need to have permissions added.
> John
> "MLi" wrote:
>> Hi all,
>> I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
>> backend database server; one Sharepoint server; one SQL Report Server web
>> server.
>> I'm going to join these 3 servers into AD domain, will it cause any
>> problem?
>> Will it break the connection between the SQL server and the other 2
>> servers?
>> Anyone has experience on this? Thanks!
>>
>> Mli
>>
>>|||Hi
The name of the instance will still be the name of the old servername,
SELECT @.@.SERVERNAME will still show the old one. That is why you need to drop
it and create the new one.
John
"MLi" wrote:
> Thanks John.
> I'm not gonna change the server name, however because it will be joined a
> domain, the DNS name will be changed. Is there any concern?
>
> MLi
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:26F04787-0DB9-4C8C-8D60-1EA65E52F8E7@.microsoft.com...
> > Hi
> >
> > If you rename the server then you will need to
> > http://msdn2.microsoft.com/en-us/library/ms143799.aspx and also change any
> > connections strings to the new name. Logins from the old workgroup may
> > need
> > removing and new ones added for the domain. Service accounts may require
> > changing and orphaned users may need to be resolved
> > http://support.microsoft.com/kb/314546. If you create any new users they
> > will
> > need to have permissions added.
> >
> > John
> >
> > "MLi" wrote:
> >
> >> Hi all,
> >>
> >> I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
> >> backend database server; one Sharepoint server; one SQL Report Server web
> >> server.
> >>
> >> I'm going to join these 3 servers into AD domain, will it cause any
> >> problem?
> >> Will it break the connection between the SQL server and the other 2
> >> servers?
> >>
> >> Anyone has experience on this? Thanks!
> >>
> >>
> >> Mli
> >>
> >>
> >>
> >>
> >>
>
>