Cluster Server installation other than default directory

Is anyone aware of any issues that can arise from installing MS SQL Server
2000 on the root of a drive - x:\\MSSQL\Data - instead of using the using
the default structure - x:\Program Files\Microsoft SQL Server\MSSQL\Data?
I have always installed to the root directory be it stand-alone or clustered
installs without any issues but I need to know whether there might be
issues especially regarding virtual sql servers installs.
Thanks
I have not seen any differences with clustering, you should be fine with any
path, as long as all possible owners have the same paths.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Gboyega Adepegba" <muyid@.hotmail.com> wrote in message
news:u5IVSaOZEHA.3752@.TK2MSFTNGP12.phx.gbl...
> Is anyone aware of any issues that can arise from installing MS SQL Server
> 2000 on the root of a drive - x:\\MSSQL\Data - instead of using the using
> the default structure - x:\Program Files\Microsoft SQL Server\MSSQL\Data?
> I have always installed to the root directory be it stand-alone or
clustered
> installs without any issues but I need to know whether there might be
> issues especially regarding virtual sql servers installs.
> Thanks
>
|||No issues. I have installed clustered instances of SQL Server 2000 on non-default locations without any problems.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way
to do this is to visit the following websites: http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
sqlsql

CLR .Net Framework 3.0

Hi

Is there any way to get the Sql 2005 to load the .Net 3.0 Framework instead of 2.0, when running a Stored Proc?

Thanks

You wouldn′t ask if you used SQLServer 2005 since beta :-) No, you can′t.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Actually the portion of the .NET Framework used by sqlclr is essentially exactly the same in .NET Framework 3.0 as .NET Framework 2.0. The BCL and CLR layers of the .NET Framework were (except for servicing fixes) unchanged and still return the same version in .NET Framework 3.0 as they did before.

See the MSDN documentation for more information on what exactly .NET Framework 3.0 entails: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnlong/html/netfx30.asp

So except for bug fixes, it doesn't matter to sqlclr whether your machine has .NET Framework 3.0 or 2.0 installed.

Steven

CLR .Net Framework 3.0

Hi

Is there any way to get the Sql 2005 to load the .Net 3.0 Framework instead of 2.0, when running a Stored Proc?

Thanks

You wouldn′t ask if you used SQLServer 2005 since beta :-) No, you can′t.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Actually the portion of the .NET Framework used by sqlclr is essentially exactly the same in .NET Framework 3.0 as .NET Framework 2.0. The BCL and CLR layers of the .NET Framework were (except for servicing fixes) unchanged and still return the same version in .NET Framework 3.0 as they did before.

See the MSDN documentation for more information on what exactly .NET Framework 3.0 entails: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnlong/html/netfx30.asp

So except for bug fixes, it doesn't matter to sqlclr whether your machine has .NET Framework 3.0 or 2.0 installed.

Steven

Client software

I have several developers that want access to my SQL server and I was
wondering instead of giving them Remote desktop access to access Enterprise
manager. I am going to install the SQL client tools locally on their PC.
My SQL server is behind a firewall, does anyone know what port needs to be
opened so I can see my SQL server in my list of available SQL servers.
Because I see all my SQL server on the local network, but not ones on other
networks.
Hope this makes some sense. Thanks for the help.
The following article answers questions related to firewall
ports:
INF: TCP Ports Needed for Communication to SQL Server
Through a Firewall
http://support.microsoft.com/?id=287932
However, what servers are listed in whatever tool drop downs
doesn't necessarily mean you have an issue with the firewall
ports. What servers are listed may not be a complete list
due to broadcast issues, network routers/subnet issues,
instances may not respond within the timeout period, etc.
The network architecture, configuration to wherever this SQL
Server box lives would be another factor.
You can always type in an IP address or a server name if a
server doesn't show up in the list.
-Sue
On Mon, 27 Feb 2006 12:38:02 -0500, "andespoint"
<andespoint@.nospam_yahoo.com> wrote:

>I have several developers that want access to my SQL server and I was
>wondering instead of giving them Remote desktop access to access Enterprise
>manager. I am going to install the SQL client tools locally on their PC.
>My SQL server is behind a firewall, does anyone know what port needs to be
>opened so I can see my SQL server in my list of available SQL servers.
>Because I see all my SQL server on the local network, but not ones on other
>networks.
>Hope this makes some sense. Thanks for the help.
>

Client software

I have several developers that want access to my SQL server and I was
wondering instead of giving them Remote desktop access to access Enterprise
manager. I am going to install the SQL client tools locally on their PC.
My SQL server is behind a firewall, does anyone know what port needs to be
opened so I can see my SQL server in my list of available SQL servers.
Because I see all my SQL server on the local network, but not ones on other
networks.
Hope this makes some sense. Thanks for the help.The following article answers questions related to firewall
ports:
INF: TCP Ports Needed for Communication to SQL Server
Through a Firewall
http://support.microsoft.com/?id=287932
However, what servers are listed in whatever tool drop downs
doesn't necessarily mean you have an issue with the firewall
ports. What servers are listed may not be a complete list
due to broadcast issues, network routers/subnet issues,
instances may not respond within the timeout period, etc.
The network architecture, configuration to wherever this SQL
Server box lives would be another factor.
You can always type in an IP address or a server name if a
server doesn't show up in the list.
-Sue
On Mon, 27 Feb 2006 12:38:02 -0500, "andespoint"
<andespoint@.nospam_yahoo.com> wrote:

>I have several developers that want access to my SQL server and I was
>wondering instead of giving them Remote desktop access to access Enterprise
>manager. I am going to install the SQL client tools locally on their PC.
>My SQL server is behind a firewall, does anyone know what port needs to be
>opened so I can see my SQL server in my list of available SQL servers.
>Because I see all my SQL server on the local network, but not ones on other
>networks.
>Hope this makes some sense. Thanks for the help.
>

Clearing all records in a table

Hi

I have two questions:

1. Is there a way to clear all records in a table from within a store procedure? (Instead of having to go into the table and manually selecting all rows and deleting them that way.)

2. I want to sort a list of records so that the only one left are the ones with just single words in. So I have used

WHERE SearchText LIKE '% %'

to remove the cells with spaces in, but I need to be able to remove the ones with punctuation too. Is there an easy way to do this?

Thanking you in advance.You can clear all records by calling

TRUNCATE TABLE tablename

or

DELETE FROM TABLE

You can do your search for punctuation the same way, adding OR searchText LIKE '%-%', etc.|||Just to be clear, is TRUNCATE TABLE a logged operation? I didn't think it was but thought I'd better check/point it out.|||Truncate table is a minimally logged operation. In a transaction, you can undo it. This transaction:

create table nisse (id int NOT NULL)
go
insert nisse select id from sysobjects
go
select count(*) from nisse
go
begin transaction
truncate table nisse
select count(*) from nisse
rollback transaction
go
select count(*) from nisse

Produces this output:

(101 row(s) affected)

----
101

(1 row(s) affected)

----
0

(1 row(s) affected)

----
101

(1 row(s) affected)|||Erm what is a "minimally logged" operation? Sorry if I'm hijacking this thread to be a teach-in for truncate table.|||The individual rows are not logged, but the data pages in use by the table are logged, and those pages are not reused until the transaction is committed.