Changing SQL2K port no. on Windows 2003

Hi,
I installed SQL2K SP3a on Windows 2003 server. During the install I changed
the SQL port number 1433 to 14330. Everything finished successfully.
But when the clients are trying to build the ODBC to connect to SQL server,
they cann't connect if they leave the Dynamically determine port check box
checked under the client configuration, but once we unchecked it and put the
port no. 14330 it will connect.
Shouldn't the Dynamically determine port no. option let the client get the
port no from the server? Or is there any security lockdown on Win2003
preventing the server to publish the port no.?
Thanks
AyadThey dynamically determine port only works for named instances. A default
instance will always default to 1433. You can change this but then the
client will always attempt to use port 1433o for every SQL Server it tries
to connect to.
If you choose to use a non-standard port for the default instance, you will
have to have each client change to connect using that port.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Changing SQL2K port no. on Windows 2003

Hi,
I installed SQL2K SP3a on Windows 2003 server. During the install I changed
the SQL port number 1433 to 14330. Everything finished successfully.
But when the clients are trying to build the ODBC to connect to SQL server,
they cann't connect if they leave the Dynamically determine port check box
checked under the client configuration, but once we unchecked it and put the
port no. 14330 it will connect.
Shouldn't the Dynamically determine port no. option let the client get the
port no from the server? Or is there any security lockdown on Win2003
preventing the server to publish the port no.?
Thanks
Ayad
They dynamically determine port only works for named instances. A default
instance will always default to 1433. You can change this but then the
client will always attempt to use port 1433o for every SQL Server it tries
to connect to.
If you choose to use a non-standard port for the default instance, you will
have to have each client change to connect using that port.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Changing SQL Server Collation

Hi
Has anyone successfully changed the Collation type for a single user
database without having to use Rebuildm.exe and/or the ALTER DATABASE
statement as I`ve tried the latter and if there are CK`s you cannot.
Thanks in advance.
Sad guy
Using ALTER DATABASE only changes the default collation for that database.
To fully change the collation you'd have to alter every column, every
character-based user-defined type, and possibly other objects (I can't
remember offhand). The easiest method I've come up with for changing the
collation is:
A) Script the entire database using Enterprise Manager
B) Edit the script and change all of the collation designators to whatever
you want
C) Create a new database using the script
D) Use DTS to transfer the data out of the old database and into the new
database
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
"ANON" <ANON@.discussions.microsoft.com> wrote in message
news:EFB1A3D2-6E98-4C81-82D1-2FF10EAC7BBF@.microsoft.com...
> Hi
> Has anyone successfully changed the Collation type for a single user
> database without having to use Rebuildm.exe and/or the ALTER DATABASE
> statement as I`ve tried the latter and if there are CK`s you cannot.
> Thanks in advance.
> Sad guy
|||Hi
Once a tables are created in a DB, ALTER DATABASE does not change those
column's collations.
What are you trying to do?
Regards
Mike
"ANON" wrote:

> Hi
> Has anyone successfully changed the Collation type for a single user
> database without having to use Rebuildm.exe and/or the ALTER DATABASE
> statement as I`ve tried the latter and if there are CK`s you cannot.
> Thanks in advance.
> Sad guy

Changing SQL Server Collation

Hi
Has anyone successfully changed the Collation type for a single user
database without having to use Rebuildm.exe and/or the ALTER DATABASE
statement as I`ve tried the latter and if there are CK`s you cannot.
Thanks in advance.
Sad guyUsing ALTER DATABASE only changes the default collation for that database.
To fully change the collation you'd have to alter every column, every
character-based user-defined type, and possibly other objects (I can't
remember offhand). The easiest method I've come up with for changing the
collation is:
A) Script the entire database using Enterprise Manager
B) Edit the script and change all of the collation designators to whatever
you want
C) Create a new database using the script
D) Use DTS to transfer the data out of the old database and into the new
database
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"ANON" <ANON@.discussions.microsoft.com> wrote in message
news:EFB1A3D2-6E98-4C81-82D1-2FF10EAC7BBF@.microsoft.com...
> Hi
> Has anyone successfully changed the Collation type for a single user
> database without having to use Rebuildm.exe and/or the ALTER DATABASE
> statement as I`ve tried the latter and if there are CK`s you cannot.
> Thanks in advance.
> Sad guy|||Hi
Once a tables are created in a DB, ALTER DATABASE does not change those
column's collations.
What are you trying to do?
Regards
Mike
"ANON" wrote:

> Hi
> Has anyone successfully changed the Collation type for a single user
> database without having to use Rebuildm.exe and/or the ALTER DATABASE
> statement as I`ve tried the latter and if there are CK`s you cannot.
> Thanks in advance.
> Sad guy

Changing SQL Server Collation

Hi
Has anyone successfully changed the Collation type for a single user
database without having to use Rebuildm.exe and/or the ALTER DATABASE
statement as I`ve tried the latter and if there are CK`s you cannot.
Thanks in advance.
Sad guyUsing ALTER DATABASE only changes the default collation for that database.
To fully change the collation you'd have to alter every column, every
character-based user-defined type, and possibly other objects (I can't
remember offhand). The easiest method I've come up with for changing the
collation is:
A) Script the entire database using Enterprise Manager
B) Edit the script and change all of the collation designators to whatever
you want
C) Create a new database using the script
D) Use DTS to transfer the data out of the old database and into the new
database
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"ANON" <ANON@.discussions.microsoft.com> wrote in message
news:EFB1A3D2-6E98-4C81-82D1-2FF10EAC7BBF@.microsoft.com...
> Hi
> Has anyone successfully changed the Collation type for a single user
> database without having to use Rebuildm.exe and/or the ALTER DATABASE
> statement as I`ve tried the latter and if there are CK`s you cannot.
> Thanks in advance.
> Sad guy|||Hi
Once a tables are created in a DB, ALTER DATABASE does not change those
column's collations.
What are you trying to do?
Regards
Mike
"ANON" wrote:
> Hi
> Has anyone successfully changed the Collation type for a single user
> database without having to use Rebuildm.exe and/or the ALTER DATABASE
> statement as I`ve tried the latter and if there are CK`s you cannot.
> Thanks in advance.
> Sad guy

Changing MOLAP dimensions to ROLAP

I have a working SSAS 2005 cube running against a small SS2005 database and successfully deployed so that it can be seen across the internet, and Excel 2002 or 2003 with the correct OLEDB provider installed can view the cube in a pivot table.

I want to be able to demonstrate that the cube dynamically updates when the underlying data changes.

I have therefore changed the measure partition to ROLAP, and now realise that I need to change the dimensions to ROLAP too. I have changed all except one of them successfully. Trying to change the last one causes SSAS2005 to crash during deployment, apparently with no explanation.

On some occasions, deploying the cube reports error:

Internal error: An unexpected error occurred (file 'mdhierarchy.cpp', line 3142, function 'MDUnmaterializedHierIter::Init'). 0 0

rather than killing SSAS2005.

If I try to specify Proactive Caching for this dimension, it gets very confused, because it reports it as a MOLAP dimension, when it isn't.

The dimension it is getting upset about accesses the database through a view.

Has anyone else run into this? If so, what can be done about it? It looks like I have found a bug in SSAS2005.

Have you tried installing SQL Server 2005 service pack 1 to see if you still get the same problem there? http://www.microsoft.com/downloads/details.aspx?familyid=cb6c71ea-d649-47ff-9176-e7cac58fd4bc&displaylang=en

If this is not working, please try and contact Customer Support to report the problem.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights

|||

Dear Edward,

Thanks for the suggestions.

The problem has shown up after upgrading to SP1, so I will have to take up your suggestion of contacting Customer Support.