Changing BLL parameter

I have inherited a web site from another developer. I am new to .net programming. Anyway I have had to add a parameter to an sql procedure and I thought i had made the change in the business logic layer correctly. I am using gridview to display and export to an excel spreadsheet. After my changes my page lets me select my parameters, but now my page come up blank, no error messages the only thing on the page are the save and export buttons.

Please help what have i missed.

Steve

You should provide more details, probably give some code excerpts for others to make suggestions.sql

Changing a 2005 db from 8.0 compatability to 9.0

I've inherited a 2005 database that is in 8.0 compatability mode. I'd like t
o
move it to 9.0 so we can do some CLR stuff. However, the upgrade advisor
won't analyze that version of SQL Server. (2005 sp1). I've looked in BOL and
I think the main thing I need to look for are the old outer join operators
(*= and =*). I've reviewed the list here:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/d686cdf0-d11d-4dba-9ec8-
de1a5f189f25.htm
and I think the join operators are the only thing that would affect me. Does
anyone have any other common issues going from 8.0 to 9.0 that I might be
missing from that list?
Thanks in advance.Also look for TOP 100 PERCENT ... ORDER BY in views. It may already be
biting you without knowing it ;-). Other than new keywords and the
deletion of the "evil join" operators, I can't think of anything else
that's common that you'd run into.
sqlboy2000 wrote:
> I've inherited a 2005 database that is in 8.0 compatability mode. I'd like
to
> move it to 9.0 so we can do some CLR stuff. However, the upgrade advisor
> won't analyze that version of SQL Server. (2005 sp1). I've looked in BOL a
nd
> I think the main thing I need to look for are the old outer join operators
> (*= and =*). I've reviewed the list here:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/d686cdf0-d11d-4dba-9ec
8-de1a5f189f25.htm
> and I think the join operators are the only thing that would affect me. Do
es
> anyone have any other common issues going from 8.0 to 9.0 that I might be
> missing from that list?
> Thanks in advance.|||We do have a few of those stupid TOP 100 percent views.
Thanks for the heads up.
"David Markle" wrote:

> Also look for TOP 100 PERCENT ... ORDER BY in views. It may already be
> biting you without knowing it ;-). Other than new keywords and the
> deletion of the "evil join" operators, I can't think of anything else
> that's common that you'd run into.
> sqlboy2000 wrote:
>

Changing a 2005 db from 8.0 compatability to 9.0

I've inherited a 2005 database that is in 8.0 compatability mode. I'd like to
move it to 9.0 so we can do some CLR stuff. However, the upgrade advisor
won't analyze that version of SQL Server. (2005 sp1). I've looked in BOL and
I think the main thing I need to look for are the old outer join operators
(*= and =*). I've reviewed the list here:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/d686cdf0-d11d-4dba-9ec8-de1a5f189f25.htm
and I think the join operators are the only thing that would affect me. Does
anyone have any other common issues going from 8.0 to 9.0 that I might be
missing from that list?
Thanks in advance.Also look for TOP 100 PERCENT ... ORDER BY in views. It may already be
biting you without knowing it ;-). Other than new keywords and the
deletion of the "evil join" operators, I can't think of anything else
that's common that you'd run into.
sqlboy2000 wrote:
> I've inherited a 2005 database that is in 8.0 compatability mode. I'd like to
> move it to 9.0 so we can do some CLR stuff. However, the upgrade advisor
> won't analyze that version of SQL Server. (2005 sp1). I've looked in BOL and
> I think the main thing I need to look for are the old outer join operators
> (*= and =*). I've reviewed the list here:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/d686cdf0-d11d-4dba-9ec8-de1a5f189f25.htm
> and I think the join operators are the only thing that would affect me. Does
> anyone have any other common issues going from 8.0 to 9.0 that I might be
> missing from that list?
> Thanks in advance.|||We do have a few of those stupid TOP 100 percent views.
Thanks for the heads up.
"David Markle" wrote:
> Also look for TOP 100 PERCENT ... ORDER BY in views. It may already be
> biting you without knowing it ;-). Other than new keywords and the
> deletion of the "evil join" operators, I can't think of anything else
> that's common that you'd run into.
> sqlboy2000 wrote:
> > I've inherited a 2005 database that is in 8.0 compatability mode. I'd like to
> > move it to 9.0 so we can do some CLR stuff. However, the upgrade advisor
> > won't analyze that version of SQL Server. (2005 sp1). I've looked in BOL and
> > I think the main thing I need to look for are the old outer join operators
> > (*= and =*). I've reviewed the list here:
> > ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/d686cdf0-d11d-4dba-9ec8-de1a5f189f25.htm
> > and I think the join operators are the only thing that would affect me. Does
> > anyone have any other common issues going from 8.0 to 9.0 that I might be
> > missing from that list?
> >
> > Thanks in advance.
>

change sqlvdi.dll IdentifySQLServer

I've inherited a SQL 2005 Server with SP2 installed that throws this error whenever it's backed up via EMC Insignia's Retrospect 7.5:

Source: SQLVDI
Event ID: 1

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY1. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=4788. Thread=4672. Client. Instance=DATALIBRARY1. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

As far as I can tell, the name should be DATALIBRARY, not DATALIBRARY1. Is there a way to change that reference without having to uninstall / reinstall?

Thanks,

- Al

If the SQL instance is named DATALIBRARY, then you'll need to look at the Retrospect configuration to see why it's using the wrong name. It may be as simple as revising the Retrospect backup job. I don't have a copy of Retrospect to play with, so I can't tell exactly how that would be done.|||Thanks Kevin. After uninstalling / re-installing the Retrospect client countless times, I was finally able to get it to sync with the SQL instance DATALIBRARY. Now I'm getting the same error message with the correct server name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other ideas / troubleshooting I can try?

Thanks,

- Al

|||Thanks Kevin.

I uninstalled / re-installed the Retrospect client and was able to get the client to sync up with the correct SQL instance name. Now the error message is the same, except that it points to the correct name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other troubleshooting you can think of?

Thanks,

- Al

|||Thanks Kevin,

I uninstalled / re-installed the Retrospect client and was able to pick up the correct SQL instance name. Now we're logging the same error with the right server name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other troubleshooting tips I can try?

Thanks,

- Al

change sqlvdi.dll IdentifySQLServer

I've inherited a SQL 2005 Server with SP2 installed that throws this error whenever it's backed up via EMC Insignia's Retrospect 7.5:

Source: SQLVDI
Event ID: 1

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY1. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=4788. Thread=4672. Client. Instance=DATALIBRARY1. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

As far as I can tell, the name should be DATALIBRARY, not DATALIBRARY1. Is there a way to change that reference without having to uninstall / reinstall?

Thanks,

- AlIf the SQL instance is named DATALIBRARY, then you'll need to look at the Retrospect configuration to see why it's using the wrong name. It may be as simple as revising the Retrospect backup job. I don't have a copy of Retrospect to play with, so I can't tell exactly how that would be done.|||Thanks Kevin. After uninstalling / re-installing the Retrospect client countless times, I was finally able to get it to sync with the SQL instance DATALIBRARY. Now I'm getting the same error message with the correct server name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other ideas / troubleshooting I can try?

Thanks,

- Al|||Thanks Kevin.

I uninstalled / re-installed the Retrospect client and was able to get the client to sync up with the correct SQL instance name. Now the error message is the same, except that it points to the correct name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other troubleshooting you can think of?

Thanks,

- Al|||Thanks Kevin,

I uninstalled / re-installed the Retrospect client and was able to pick up the correct SQL instance name. Now we're logging the same error with the right server name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other troubleshooting tips I can try?

Thanks,

- Al

change sqlvdi.dll IdentifySQLServer

I've inherited a SQL 2005 Server with SP2 installed that throws this error whenever it's backed up via EMC Insignia's Retrospect 7.5:

Source: SQLVDI
Event ID: 1

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY1. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=4788. Thread=4672. Client. Instance=DATALIBRARY1. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

As far as I can tell, the name should be DATALIBRARY, not DATALIBRARY1. Is there a way to change that reference without having to uninstall / reinstall?

Thanks,

- AlIf the SQL instance is named DATALIBRARY, then you'll need to look at the Retrospect configuration to see why it's using the wrong name. It may be as simple as revising the Retrospect backup job. I don't have a copy of Retrospect to play with, so I can't tell exactly how that would be done.|||Thanks Kevin. After uninstalling / re-installing the Retrospect client countless times, I was finally able to get it to sync with the SQL instance DATALIBRARY. Now I'm getting the same error message with the correct server name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other ideas / troubleshooting I can try?

Thanks,

- Al|||Thanks Kevin.

I uninstalled / re-installed the Retrospect client and was able to get the client to sync up with the correct SQL instance name. Now the error message is the same, except that it points to the correct name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other troubleshooting you can think of?

Thanks,

- Al|||Thanks Kevin,

I uninstalled / re-installed the Retrospect client and was able to pick up the correct SQL instance name. Now we're logging the same error with the right server name:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$DATALIBRARY. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=2540. Thread=2760. Client. Instance=DATALIBRARY. VD=.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any other troubleshooting tips I can try?

Thanks,

- Al