Named instance question

Can instance names be aliased back to the the default instance? ie can
server/instancename resolve back to servername/? We are looking to migrate
over from using a named instance, to a default instance, but don't want to
have to go change all of the connection strings in many applications, to
that have named instances attached.
If so, can someone point me in the direction to do so?Only from the clients connecting to it. You can install MDAC 2.6 or later
and use the alias.
"Gary" <clgary@.yahoo.com> wrote in message
news:#j9tS57uEHA.1404@.TK2MSFTNGP11.phx.gbl...
> Can instance names be aliased back to the the default instance? ie can
> server/instancename resolve back to servername/? We are looking to migrate
> over from using a named instance, to a default instance, but don't want to
> have to go change all of the connection strings in many applications, to
> that have named instances attached.
> If so, can someone point me in the direction to do so?
>

Named instance question

Can instance names be aliased back to the the default instance? ie can
server/instancename resolve back to servername/? We are looking to migrate
over from using a named instance, to a default instance, but don't want to
have to go change all of the connection strings in many applications, to
that have named instances attached.
If so, can someone point me in the direction to do so?Only from the clients connecting to it. You can install MDAC 2.6 or later
and use the alias.
"Gary" <clgary@.yahoo.com> wrote in message
news:#j9tS57uEHA.1404@.TK2MSFTNGP11.phx.gbl...
> Can instance names be aliased back to the the default instance? ie can
> server/instancename resolve back to servername/? We are looking to migrate
> over from using a named instance, to a default instance, but don't want to
> have to go change all of the connection strings in many applications, to
> that have named instances attached.
> If so, can someone point me in the direction to do so?
>

Named instance question

Can instance names be aliased back to the the default instance? ie can
server/instancename resolve back to servername/? We are looking to migrate
over from using a named instance, to a default instance, but don't want to
have to go change all of the connection strings in many applications, to
that have named instances attached.
If so, can someone point me in the direction to do so?
Only from the clients connecting to it. You can install MDAC 2.6 or later
and use the alias.
"Gary" <clgary@.yahoo.com> wrote in message
news:#j9tS57uEHA.1404@.TK2MSFTNGP11.phx.gbl...
> Can instance names be aliased back to the the default instance? ie can
> server/instancename resolve back to servername/? We are looking to migrate
> over from using a named instance, to a default instance, but don't want to
> have to go change all of the connection strings in many applications, to
> that have named instances attached.
> If so, can someone point me in the direction to do so?
>

Name and Description property of OLEDB Source components

I am adding two OLE DB Source components to my pipeline and giving them different names

(via the Sourcename variable) but like they are assuming default name and description i.e. OLE DB Source which is causing the following error message on opening the package that was generated.

The package contains two objects with the duplicate name of "component "OLE DB Source" (37)" and "component "OLE DB Source" (1)"

Here is how I am doing it, in the debugger the names in both instances seem to have set correctly based on the variable but when saved they are lost. What am I doing wrong here?

IDTSComponentMetaData90 source = dataFlowTask.ComponentMetaDataCollection.New();

source.Name = Sourcename;

source.ComponentClassID = "DTSAdapter.OleDbSource.1";

source.Description = Sourcename;

Thanks

Just figured it out. So if anyone else is running into this you need to be aware of the fact that the name you provide to the IDTSComponentMetaData90 is reinitialized after you get the design time instance of the component.

So the Name and other properties have to be assigned after the design time instance is created.

Mysterious Views

I have two views in a production database that I did not create and I cannot account for. From the names used and the syntax of the views, it seems that the system (SQL Server) generated them.

Name: _hypmv_0_5771
Name: _hypmv_0

The syntax crushes the entire SELECT statement (4357 characters) onto a single line of T-SQL (not something I'm usually in the habit of doing).

I have read on kbAlertz that there was a bug in the original release of SQL server where the Index Tuning Wizard did not always remove hypothetical indices used to calculate performance improvements. I have not found anything related to hypothetical views. I do have indexed views, but none that reference these views.

I have checked dependencies; nothing depends on these views and they, in turn, do not depend on anything else.

Has anyone else encountered this problem? Aside from saving the definitions and then dropping them (just to see what may break), are there any suggestions for how to deal with this?

The database is medium-large. About 25GB.

Thanks,

Hugh ScottHere is the article on hypothetical indexes...

http://support.microsoft.com/?id=290414

Mysterious indexes "_WA_Sys_..."

I was looking for tables with no indexes, and I keep
finding entries in sysindexes with names
like "_WA_Sys_....", which I certainly don't create.
The last one is possibly attached to a column defined as
nvarchar(128), but its the only column in the table
defined that way, and the other columns don't have such an
index ! very confusing.
Does anyone know what these are ?
Does anyone have an SQL script that will correctly!
identify tables without indexes ? This would be hugely
appreciated !_WA_Sys_...." are SQL Server statstics. You have AUTO Stats turned on.
This is expected. You should leave them alone.
"Jim Trowbridge" <jtrowbridge@.adelaidebank.com.au> wrote in message
news:07be01c36600$78857070$a401280a@.phx.gbl...
I was looking for tables with no indexes, and I keep
finding entries in sysindexes with names
like "_WA_Sys_....", which I certainly don't create.
The last one is possibly attached to a column defined as
nvarchar(128), but its the only column in the table
defined that way, and the other columns don't have such an
index ! very confusing.
Does anyone know what these are ?
Does anyone have an SQL script that will correctly!
identify tables without indexes ? This would be hugely
appreciated !