Downgrading SQLServer to MSDE

Hi,
I am pretty new to MSDE and am just researching options for writing a .NET
version of a desktop application (currently VB6 / Access).
There is a web version of our product available already which has a SQL
Server backend.
I am figuring that I will use MSDE so I can use all their Stored procedures
and as much code of theirs as possible.
What I am wondering is if I can get downgrade from SQL Server to MSDE ?
There's lots of information about upgrading, but nothing about downgrading.
Thanks
Sanj
hi,
Sanjit Suchak wrote:
> Hi,
> I am pretty new to MSDE and am just researching options for writing a
> .NET version of a desktop application (currently VB6 / Access).
> There is a web version of our product available already which has a
> SQL Server backend.
> I am figuring that I will use MSDE so I can use all their Stored
> procedures and as much code of theirs as possible.
> What I am wondering is if I can get downgrade from SQL Server to MSDE
> ? There's lots of information about upgrading, but nothing about
> downgrading.
downgrading is a viable solution as long as you take into consideration all
relevant MSDE limitations..
2gb database size, limited replication support, no OLAP features, no
Reporting Services... and limited number of users scenarios... these are the
most relevant of them in my opinion... but the core features are all
available...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Downgrading sql server 2005

Hi
Would any .net application developed for sql server 20005 server edition
work on sql server 2005 express edition? This is in case the target client
does not have a license of sql server 2005 server edition.
Thanks
Regards
It′s a bit different as the differences in SQL Server 200 vs. MSDE.
The main features are also build in SQL Server 2005 Express, but some are
cut (there has to be a reason to buy the full featured product ;-) )
http://msdn.microsoft.com/library/de...seoverview.asp
There is a section naming: "Features not present in SQL Server Express", you
should check if there are some feature named that youwant to use in your
deployable application.
HTH, jens Suessmeyer.
http://www.sqlserver2005.de

Downgrading sql server 2005

Hi
Would any .net application developed for sql server 20005 server edition
work on sql server 2005 express edition? This is in case the target client
does not have a license of sql server 2005 server edition.
Thanks
RegardsIt′s a bit different as the differences in SQL Server 200 vs. MSDE.
The main features are also build in SQL Server 2005 Express, but some are
cut (there has to be a reason to buy the full featured product ;-) )
http://msdn.microsoft.com/library/d...r />
rview.asp
There is a section naming: "Features not present in SQL Server Express", you
should check if there are some feature named that youwant to use in your
deployable application.
HTH, jens Suessmeyer.
http://www.sqlserver2005.de
--sql

Downgrading sql server 2005

Hi
Would any .net application developed for sql server 20005 server edition
work on sql server 2005 express edition? This is in case the target client
does not have a license of sql server 2005 server edition.
Thanks
RegardsIt´s a bit different as the differences in SQL Server 200 vs. MSDE.
The main features are also build in SQL Server 2005 Express, but some are
cut (there has to be a reason to buy the full featured product ;-) )
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsse/html/sseoverview.asp
There is a section naming: "Features not present in SQL Server Express", you
should check if there are some feature named that youwant to use in your
deployable application.
HTH, jens Suessmeyer.
--
http://www.sqlserver2005.de
--

Downgrading MSSQL 2005 DB to MSSQL 2000 DB

Hello all,
Does anybody have any experience in trying to backup a DB from MSSQL
2005 and then restoring it on a machine with MSSQL 2000? Can it be
done? Is it completely impossible?
While at it - Is it possible to do the reverse without problems? Is
MSSQL 2005 100% back-compatible with MSSQL 2000, so I can just backup a
whole DB on MSSQL 2000, restore it on MSSQL 2005 and have it run as
smoothly?
Thanks in advance.You can go from 2000 to 2005 and the db will be upgraded to the 2005 format.
But once it is in the 2005 format you can not go backwards. The upgrade is
seamless in and of itself but there may be incompatibilities with your
existing code / app that you might have to deal with. You can use the
upgrade advisor to see first.
http://www.microsoft.com/downloads/details.aspx?familyid=63FCE120-5E87-4AF1-B080-CA461AEAFAA2&displaylang=en
--
Andrew J. Kelly SQL MVP
<Baudolino@.gmail.com> wrote in message
news:1128954487.426069.160440@.f14g2000cwb.googlegroups.com...
> Hello all,
> Does anybody have any experience in trying to backup a DB from MSSQL
> 2005 and then restoring it on a machine with MSSQL 2000? Can it be
> done? Is it completely impossible?
> While at it - Is it possible to do the reverse without problems? Is
> MSSQL 2005 100% back-compatible with MSSQL 2000, so I can just backup a
> whole DB on MSSQL 2000, restore it on MSSQL 2005 and have it run as
> smoothly?
> Thanks in advance.
>

Downgrading MSSQL 2005 DB to MSSQL 2000 DB

Hello all,
Does anybody have any experience in trying to backup a DB from MSSQL
2005 and then restoring it on a machine with MSSQL 2000? Can it be
done? Is it completely impossible?
While at it - Is it possible to do the reverse without problems? Is
MSSQL 2005 100% back-compatible with MSSQL 2000, so I can just backup a
whole DB on MSSQL 2000, restore it on MSSQL 2005 and have it run as
smoothly?
Thanks in advance.
You can go from 2000 to 2005 and the db will be upgraded to the 2005 format.
But once it is in the 2005 format you can not go backwards. The upgrade is
seamless in and of itself but there may be incompatibilities with your
existing code / app that you might have to deal with. You can use the
upgrade advisor to see first.
http://www.microsoft.com/downloads/d...displaylang=en
Andrew J. Kelly SQL MVP
<Baudolino@.gmail.com> wrote in message
news:1128954487.426069.160440@.f14g2000cwb.googlegr oups.com...
> Hello all,
> Does anybody have any experience in trying to backup a DB from MSSQL
> 2005 and then restoring it on a machine with MSSQL 2000? Can it be
> done? Is it completely impossible?
> While at it - Is it possible to do the reverse without problems? Is
> MSSQL 2005 100% back-compatible with MSSQL 2000, so I can just backup a
> whole DB on MSSQL 2000, restore it on MSSQL 2005 and have it run as
> smoothly?
> Thanks in advance.
>

Downgrading MSSQL 2005 DB to MSSQL 2000 DB

Hello all,
Does anybody have any experience in trying to backup a DB from MSSQL
2005 and then restoring it on a machine with MSSQL 2000? Can it be
done? Is it completely impossible?
While at it - Is it possible to do the reverse without problems? Is
MSSQL 2005 100% back-compatible with MSSQL 2000, so I can just backup a
whole DB on MSSQL 2000, restore it on MSSQL 2005 and have it run as
smoothly?
Thanks in advance.You can go from 2000 to 2005 and the db will be upgraded to the 2005 format.
But once it is in the 2005 format you can not go backwards. The upgrade is
seamless in and of itself but there may be incompatibilities with your
existing code / app that you might have to deal with. You can use the
upgrade advisor to see first.
http://www.microsoft.com/downloads/...&displaylang=en
--
Andrew J. Kelly SQL MVP
<Baudolino@.gmail.com> wrote in message
news:1128954487.426069.160440@.f14g2000cwb.googlegroups.com...
> Hello all,
> Does anybody have any experience in trying to backup a DB from MSSQL
> 2005 and then restoring it on a machine with MSSQL 2000? Can it be
> done? Is it completely impossible?
> While at it - Is it possible to do the reverse without problems? Is
> MSSQL 2005 100% back-compatible with MSSQL 2000, so I can just backup a
> whole DB on MSSQL 2000, restore it on MSSQL 2005 and have it run as
> smoothly?
> Thanks in advance.
>

Downgrading MDAC on an XP machine

i was wondering if there is anyway to downgrade the MDAC to 2.5 (or specicifically the sqlsrv32.dll to 3.70.06.23) on an XP machine?
WHY? - http://www.dbforums.com/t1043791.htmlno suggestions on how i can install an earlier version of sqlsrv32.dll on an XP machine?sql

Downgrading from enterprise to standard

Hi all,
I need to go from an enterprise edition of sql to a standard edition. Has anyone been through this process? is there an easy way to do this? or do I need to script all my jobs and logins etc and rebuild them later?
thanks in advance,
DanielBackup datbases and rebuild, sucks ass thank microsoft

Downgrading from Enterprise to Standard

Hi
Does anyone know how to go from SQL Server 2000 Enterprise to Standard and restore all of the databases? I've tried restoring the Mater Database, but I am getting the following
The backup of the system database on device XXXX cannot be restored because it was created by a different version of the server (134217546) than this server (134217488)
KB article 264474 shows how to get a server back to the version level, if the flavor of SQL Server is the same [i.e. Enterprise] but not if the server is being downgraded from Enterprise to Standard for licensing reasons
Thanks
ChrisChris,
This appears to be backup / restore that is the problem.
You should be able to detach the databases from the SS2KEE server and then
attach them to the SS2KSt server. Check this article (from the BOL) on
Attaching and Detaching Databases. The file formats are the same.
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/createdb/cm_8_des_03_89pv.asp
Russell Fields
"Chris Smith" <chriss@.resultmatrix.com> wrote in message
news:D8C2FF80-CA31-495C-9B6D-2F4D9172FA84@.microsoft.com...
> Hi,
> Does anyone know how to go from SQL Server 2000 Enterprise to Standard and
restore all of the databases? I've tried restoring the Mater Database, but
I am getting the following:
> The backup of the system database on device XXXX cannot be restored
because it was created by a different version of the server (134217546) than
this server (134217488).
> KB article 264474 shows how to get a server back to the version level, if
the flavor of SQL Server is the same [i.e. Enterprise] but not if the
server is being downgraded from Enterprise to Standard for licensing
reasons.
> Thanks,
> Chris|||I would double check that you really have the same service pack/hotfix level. This is what the error
implies.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Chris Smith" <chriss@.resultmatrix.com> wrote in message
news:D8C2FF80-CA31-495C-9B6D-2F4D9172FA84@.microsoft.com...
> Hi,
> Does anyone know how to go from SQL Server 2000 Enterprise to Standard and restore all of the
databases? I've tried restoring the Mater Database, but I am getting the following:
> The backup of the system database on device XXXX cannot be restored because it was created by a
different version of the server (134217546) than this server (134217488).
> KB article 264474 shows how to get a server back to the version level, if the flavor of SQL Server
is the same [i.e. Enterprise] but not if the server is being downgraded from Enterprise to Standard
for licensing reasons.
> Thanks,
> Chris

downgrading from 2005 to sql server express

Hi

I have a sql server 2005 database - i want to downgrade it to sql server express , i ahve tried to do a restore from a backup file from the 2005 database , I basically want to restore tables stored procs and data from the 2005 into sql server express , any ideas on the best direction for this ?

thanks

If both SQL Servers are in the same network you just register the Express with the full version and in the backup and restore wizard choose the restore from device option. If both are not in the same network then you take the .bak file and put it in the backup subfolder in Microsoft SQL Server and it is important you let Windows create the file path for you and follow the previous direction. Post again if you still have question. Hope this helps.

Downgrade sql2000 to sql7

I have a sql2000 server that I am contemplating downgrading to sql7...
The scenario is this:
The server was originally NT4, upgraded to Server2000.
The server ran Accountmate using SQL7.
SQL was upgraded to 2000.
Turns out that the SQL2000 is not entirely compatible with the Accountmate -
I don't have the exact reasons why. The application generates an error
about a login name on startup. The user clicks ok, then continues without a
problem.
The client and Accountmate reps elected to leave as is. It has been about
two years now!
With the exception of adding data, no modifications have been made to the
databases since.
Is it possible to do the downgrade?
What are the implications of doing?
Where would I go to get specifics to the procedure?
Thanks in advance for any help.
Bruce.
Hi
You are downgrading to a product that will come to the end of it's life
sooner than the one you are on, which can't be good. I assume you are not
paying anything for the support of this package? If the login issue is your
only problem then I would try to find out why this happens rather than hoping
a downgrade will solve it. Do you get anything written into the SQL server
log or an specific error message/number?
John
"B. Horstmanshof" wrote:

> I have a sql2000 server that I am contemplating downgrading to sql7...
> The scenario is this:
> The server was originally NT4, upgraded to Server2000.
> The server ran Accountmate using SQL7.
> SQL was upgraded to 2000.
> Turns out that the SQL2000 is not entirely compatible with the Accountmate -
> I don't have the exact reasons why. The application generates an error
> about a login name on startup. The user clicks ok, then continues without a
> problem.
> The client and Accountmate reps elected to leave as is. It has been about
> two years now!
> With the exception of adding data, no modifications have been made to the
> databases since.
> Is it possible to do the downgrade?
> What are the implications of doing?
> Where would I go to get specifics to the procedure?
> Thanks in advance for any help.
> Bruce.
>
>
|||Hi John.
We are not paying support for this package. The pop-up error claims to be a
connectivity error:
Error # [1526]: Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL
Server]Invalid column name 'suid'.
SQL Stmt:
select name from sysusers where suid in (select suid master..sysusers where
name='vamlogin') and name='dbo'
They way it was explained to me is (as best I remember) that the name is
used for something else or can't be used in SQL2000, but must exisit with
this version of Accountmate. It was a while ago, and nobody seemed worried
about it!
Ideally the client would upgrade the software and move to 2003, but it is
always a money issue - they would need to upgrade servers, o/s, sql and
application, and they can't see the benefit of spending that kind of money!
The backwards move would be to put the application on the platform it was
supposed to be on, and see if the performance issues disappear.
Bruce
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:A66A999D-2C70-4995-940A-387F58312CA4@.microsoft.com...
> Hi
> You are downgrading to a product that will come to the end of it's life
> sooner than the one you are on, which can't be good. I assume you are not
> paying anything for the support of this package? If the login issue is
your
> only problem then I would try to find out why this happens rather than
hoping[vbcol=seagreen]
> a downgrade will solve it. Do you get anything written into the SQL server
> log or an specific error message/number?
> John
>
> "B. Horstmanshof" wrote:
Accountmate -[vbcol=seagreen]
without a[vbcol=seagreen]
about[vbcol=seagreen]
the[vbcol=seagreen]
|||Hi Bruce
As they are querying the system catalogs directly then you can't easily
overcome this unless it is in a stored procedure where the code can be
changed. it looks like it is checking the user is in the dbo which could be
found by other methods.
If this does not affect the functionality why would you want to revert back?
John
"B. Horstmanshof" wrote:

> Hi John.
> We are not paying support for this package. The pop-up error claims to be a
> connectivity error:
> Error # [1526]: Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL
> Server]Invalid column name 'suid'.
> SQL Stmt:
> select name from sysusers where suid in (select suid master..sysusers where
> name='vamlogin') and name='dbo'
> They way it was explained to me is (as best I remember) that the name is
> used for something else or can't be used in SQL2000, but must exisit with
> this version of Accountmate. It was a while ago, and nobody seemed worried
> about it!
> Ideally the client would upgrade the software and move to 2003, but it is
> always a money issue - they would need to upgrade servers, o/s, sql and
> application, and they can't see the benefit of spending that kind of money!
> The backwards move would be to put the application on the platform it was
> supposed to be on, and see if the performance issues disappear.
> Bruce
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:A66A999D-2C70-4995-940A-387F58312CA4@.microsoft.com...
> your
> hoping
> Accountmate -
> without a
> about
> the
>
>
|||The server is having problems - slow and apparently stalling. I have
noticed that the cpu usage on the system remain high for minutes at a time.
There is a second server with the same setup (but using sql7) that is for a
separate company in the same network. The databases are similar in size and
no one is having a problem with that system.
I figure that if I have to rebuild or reinstall things, I should give the
apps what they want (namely sql7).
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:A1B28A17-7343-4569-B8AF-0E2FE8D9E3C4@.microsoft.com...
> Hi Bruce
> As they are querying the system catalogs directly then you can't easily
> overcome this unless it is in a stored procedure where the code can be
> changed. it looks like it is checking the user is in the dbo which could
be
> found by other methods.
> If this does not affect the functionality why would you want to revert
back?[vbcol=seagreen]
> John
>
> "B. Horstmanshof" wrote:
be a[vbcol=seagreen]
Driver][SQL[vbcol=seagreen]
where[vbcol=seagreen]
with[vbcol=seagreen]
worried[vbcol=seagreen]
is[vbcol=seagreen]
money![vbcol=seagreen]
was[vbcol=seagreen]
life[vbcol=seagreen]
not[vbcol=seagreen]
server[vbcol=seagreen]
sql7...[vbcol=seagreen]
error[vbcol=seagreen]
to[vbcol=seagreen]
|||Hi Bruce,
What sort of maintenance is is undertaken on this database?
John
"B. Horstmanshof" wrote:

> The server is having problems - slow and apparently stalling. I have
> noticed that the cpu usage on the system remain high for minutes at a time.
> There is a second server with the same setup (but using sql7) that is for a
> separate company in the same network. The databases are similar in size and
> no one is having a problem with that system.
> I figure that if I have to rebuild or reinstall things, I should give the
> apps what they want (namely sql7).
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:A1B28A17-7343-4569-B8AF-0E2FE8D9E3C4@.microsoft.com...
> be
> back?
> be a
> Driver][SQL
> where
> with
> worried
> is
> money!
> was
> life
> not
> server
> sql7...
> error
> to
>
>
|||Just backups (to disk) and optimization (reorganize pages and change free
space to 10%), both run through the Database maintenance plan on a daily
schedule.
The Application vendor takes care of that end - so I hope I answered the
question correctly!
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:56E40227-C36C-408C-970E-6EDDE317BB66@.microsoft.com...[vbcol=seagreen]
> Hi Bruce,
> What sort of maintenance is is undertaken on this database?
> John
> "B. Horstmanshof" wrote:
time.[vbcol=seagreen]
for a[vbcol=seagreen]
and[vbcol=seagreen]
the[vbcol=seagreen]
easily[vbcol=seagreen]
could[vbcol=seagreen]
to[vbcol=seagreen]
master..sysusers[vbcol=seagreen]
name is[vbcol=seagreen]
it[vbcol=seagreen]
and[vbcol=seagreen]
it[vbcol=seagreen]
are[vbcol=seagreen]
issue is[vbcol=seagreen]
than[vbcol=seagreen]
SQL[vbcol=seagreen]
an[vbcol=seagreen]
continues[vbcol=seagreen]
been[vbcol=seagreen]
made[vbcol=seagreen]
|||Hi
If the jobs have not been failing then it sounds like it should be ok, have
you tried profiler to identify slow queries and missing indexes/statistics?
John
"B. Horstmanshof" wrote:

> Just backups (to disk) and optimization (reorganize pages and change free
> space to 10%), both run through the Database maintenance plan on a daily
> schedule.
> The Application vendor takes care of that end - so I hope I answered the
> question correctly!
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:56E40227-C36C-408C-970E-6EDDE317BB66@.microsoft.com...
> time.
> for a
> and
> the
> easily
> could
> to
> master..sysusers
> name is
> it
> and
> it
> are
> issue is
> than
> SQL
> an
> continues
> been
> made
>
>
|||John,
I found the problem... unrelated of course. Turns out that Surfcontrol
Spam filter is using a database on the server and that is what is stressing
the server! I can move it to a local msde datbase on the SurfControl
Server.
I appreciate your input - I would probably not found this so quickly without
it.
Many Thanks
Bruce
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:29CB601C-C569-4625-8E82-9C68CE01EEE1@.microsoft.com...
> Hi
> If the jobs have not been failing then it sounds like it should be ok,
have
> you tried profiler to identify slow queries and missing
indexes/statistics?[vbcol=seagreen]
> John
> "B. Horstmanshof" wrote:
free[vbcol=seagreen]
have[vbcol=seagreen]
a[vbcol=seagreen]
is[vbcol=seagreen]
size[vbcol=seagreen]
give[vbcol=seagreen]
can be[vbcol=seagreen]
revert[vbcol=seagreen]
claims[vbcol=seagreen]
exisit[vbcol=seagreen]
seemed[vbcol=seagreen]
but[vbcol=seagreen]
sql[vbcol=seagreen]
kind of[vbcol=seagreen]
platform[vbcol=seagreen]
it's[vbcol=seagreen]
you[vbcol=seagreen]
rather[vbcol=seagreen]
the[vbcol=seagreen]
to[vbcol=seagreen]
the[vbcol=seagreen]
generates[vbcol=seagreen]
has[vbcol=seagreen]
been[vbcol=seagreen]

Downgrade sql2000 to sql7

I have a sql2000 server that I am contemplating downgrading to sql7...
The scenario is this:
The server was originally NT4, upgraded to Server2000.
The server ran Accountmate using SQL7.
SQL was upgraded to 2000.
Turns out that the SQL2000 is not entirely compatible with the Accountmate -
I don't have the exact reasons why. The application generates an error
about a login name on startup. The user clicks ok, then continues without a
problem.
The client and Accountmate reps elected to leave as is. It has been about
two years now!
With the exception of adding data, no modifications have been made to the
databases since.
Is it possible to do the downgrade?
What are the implications of doing?
Where would I go to get specifics to the procedure?
Thanks in advance for any help.
Bruce.Hi
You are downgrading to a product that will come to the end of it's life
sooner than the one you are on, which can't be good. I assume you are not
paying anything for the support of this package? If the login issue is your
only problem then I would try to find out why this happens rather than hoping
a downgrade will solve it. Do you get anything written into the SQL server
log or an specific error message/number?
John
"B. Horstmanshof" wrote:
> I have a sql2000 server that I am contemplating downgrading to sql7...
> The scenario is this:
> The server was originally NT4, upgraded to Server2000.
> The server ran Accountmate using SQL7.
> SQL was upgraded to 2000.
> Turns out that the SQL2000 is not entirely compatible with the Accountmate -
> I don't have the exact reasons why. The application generates an error
> about a login name on startup. The user clicks ok, then continues without a
> problem.
> The client and Accountmate reps elected to leave as is. It has been about
> two years now!
> With the exception of adding data, no modifications have been made to the
> databases since.
> Is it possible to do the downgrade?
> What are the implications of doing?
> Where would I go to get specifics to the procedure?
> Thanks in advance for any help.
> Bruce.
>
>|||Hi John.
We are not paying support for this package. The pop-up error claims to be a
connectivity error:
Error # [1526]: Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL
Server]Invalid column name 'suid'.
SQL Stmt:
select name from sysusers where suid in (select suid master..sysusers where
name='vamlogin') and name='dbo'
They way it was explained to me is (as best I remember) that the name is
used for something else or can't be used in SQL2000, but must exisit with
this version of Accountmate. It was a while ago, and nobody seemed worried
about it!
Ideally the client would upgrade the software and move to 2003, but it is
always a money issue - they would need to upgrade servers, o/s, sql and
application, and they can't see the benefit of spending that kind of money!
The backwards move would be to put the application on the platform it was
supposed to be on, and see if the performance issues disappear.
Bruce
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:A66A999D-2C70-4995-940A-387F58312CA4@.microsoft.com...
> Hi
> You are downgrading to a product that will come to the end of it's life
> sooner than the one you are on, which can't be good. I assume you are not
> paying anything for the support of this package? If the login issue is
your
> only problem then I would try to find out why this happens rather than
hoping
> a downgrade will solve it. Do you get anything written into the SQL server
> log or an specific error message/number?
> John
>
> "B. Horstmanshof" wrote:
> > I have a sql2000 server that I am contemplating downgrading to sql7...
> >
> > The scenario is this:
> > The server was originally NT4, upgraded to Server2000.
> > The server ran Accountmate using SQL7.
> > SQL was upgraded to 2000.
> >
> > Turns out that the SQL2000 is not entirely compatible with the
Accountmate -
> > I don't have the exact reasons why. The application generates an error
> > about a login name on startup. The user clicks ok, then continues
without a
> > problem.
> > The client and Accountmate reps elected to leave as is. It has been
about
> > two years now!
> >
> > With the exception of adding data, no modifications have been made to
the
> > databases since.
> >
> > Is it possible to do the downgrade?
> > What are the implications of doing?
> > Where would I go to get specifics to the procedure?
> >
> > Thanks in advance for any help.
> > Bruce.
> >
> >
> >|||Hi Bruce
As they are querying the system catalogs directly then you can't easily
overcome this unless it is in a stored procedure where the code can be
changed. it looks like it is checking the user is in the dbo which could be
found by other methods.
If this does not affect the functionality why would you want to revert back?
John
"B. Horstmanshof" wrote:
> Hi John.
> We are not paying support for this package. The pop-up error claims to be a
> connectivity error:
> Error # [1526]: Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL
> Server]Invalid column name 'suid'.
> SQL Stmt:
> select name from sysusers where suid in (select suid master..sysusers where
> name='vamlogin') and name='dbo'
> They way it was explained to me is (as best I remember) that the name is
> used for something else or can't be used in SQL2000, but must exisit with
> this version of Accountmate. It was a while ago, and nobody seemed worried
> about it!
> Ideally the client would upgrade the software and move to 2003, but it is
> always a money issue - they would need to upgrade servers, o/s, sql and
> application, and they can't see the benefit of spending that kind of money!
> The backwards move would be to put the application on the platform it was
> supposed to be on, and see if the performance issues disappear.
> Bruce
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:A66A999D-2C70-4995-940A-387F58312CA4@.microsoft.com...
> > Hi
> >
> > You are downgrading to a product that will come to the end of it's life
> > sooner than the one you are on, which can't be good. I assume you are not
> > paying anything for the support of this package? If the login issue is
> your
> > only problem then I would try to find out why this happens rather than
> hoping
> > a downgrade will solve it. Do you get anything written into the SQL server
> > log or an specific error message/number?
> >
> > John
> >
> >
> >
> > "B. Horstmanshof" wrote:
> >
> > > I have a sql2000 server that I am contemplating downgrading to sql7...
> > >
> > > The scenario is this:
> > > The server was originally NT4, upgraded to Server2000.
> > > The server ran Accountmate using SQL7.
> > > SQL was upgraded to 2000.
> > >
> > > Turns out that the SQL2000 is not entirely compatible with the
> Accountmate -
> > > I don't have the exact reasons why. The application generates an error
> > > about a login name on startup. The user clicks ok, then continues
> without a
> > > problem.
> > > The client and Accountmate reps elected to leave as is. It has been
> about
> > > two years now!
> > >
> > > With the exception of adding data, no modifications have been made to
> the
> > > databases since.
> > >
> > > Is it possible to do the downgrade?
> > > What are the implications of doing?
> > > Where would I go to get specifics to the procedure?
> > >
> > > Thanks in advance for any help.
> > > Bruce.
> > >
> > >
> > >
>
>|||The server is having problems - slow and apparently stalling. I have
noticed that the cpu usage on the system remain high for minutes at a time.
There is a second server with the same setup (but using sql7) that is for a
separate company in the same network. The databases are similar in size and
no one is having a problem with that system.
I figure that if I have to rebuild or reinstall things, I should give the
apps what they want (namely sql7).
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:A1B28A17-7343-4569-B8AF-0E2FE8D9E3C4@.microsoft.com...
> Hi Bruce
> As they are querying the system catalogs directly then you can't easily
> overcome this unless it is in a stored procedure where the code can be
> changed. it looks like it is checking the user is in the dbo which could
be
> found by other methods.
> If this does not affect the functionality why would you want to revert
back?
> John
>
> "B. Horstmanshof" wrote:
> > Hi John.
> >
> > We are not paying support for this package. The pop-up error claims to
be a
> > connectivity error:
> >
> > Error # [1526]: Connectivity error: [Microsoft][ODBC SQL Server
Driver][SQL
> > Server]Invalid column name 'suid'.
> >
> > SQL Stmt:
> > select name from sysusers where suid in (select suid master..sysusers
where
> > name='vamlogin') and name='dbo'
> >
> > They way it was explained to me is (as best I remember) that the name is
> > used for something else or can't be used in SQL2000, but must exisit
with
> > this version of Accountmate. It was a while ago, and nobody seemed
worried
> > about it!
> >
> > Ideally the client would upgrade the software and move to 2003, but it
is
> > always a money issue - they would need to upgrade servers, o/s, sql and
> > application, and they can't see the benefit of spending that kind of
money!
> >
> > The backwards move would be to put the application on the platform it
was
> > supposed to be on, and see if the performance issues disappear.
> >
> > Bruce
> >
> >
> > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > news:A66A999D-2C70-4995-940A-387F58312CA4@.microsoft.com...
> > > Hi
> > >
> > > You are downgrading to a product that will come to the end of it's
life
> > > sooner than the one you are on, which can't be good. I assume you are
not
> > > paying anything for the support of this package? If the login issue is
> > your
> > > only problem then I would try to find out why this happens rather than
> > hoping
> > > a downgrade will solve it. Do you get anything written into the SQL
server
> > > log or an specific error message/number?
> > >
> > > John
> > >
> > >
> > >
> > > "B. Horstmanshof" wrote:
> > >
> > > > I have a sql2000 server that I am contemplating downgrading to
sql7...
> > > >
> > > > The scenario is this:
> > > > The server was originally NT4, upgraded to Server2000.
> > > > The server ran Accountmate using SQL7.
> > > > SQL was upgraded to 2000.
> > > >
> > > > Turns out that the SQL2000 is not entirely compatible with the
> > Accountmate -
> > > > I don't have the exact reasons why. The application generates an
error
> > > > about a login name on startup. The user clicks ok, then continues
> > without a
> > > > problem.
> > > > The client and Accountmate reps elected to leave as is. It has been
> > about
> > > > two years now!
> > > >
> > > > With the exception of adding data, no modifications have been made
to
> > the
> > > > databases since.
> > > >
> > > > Is it possible to do the downgrade?
> > > > What are the implications of doing?
> > > > Where would I go to get specifics to the procedure?
> > > >
> > > > Thanks in advance for any help.
> > > > Bruce.
> > > >
> > > >
> > > >
> >
> >
> >|||Hi Bruce,
What sort of maintenance is is undertaken on this database?
John
"B. Horstmanshof" wrote:
> The server is having problems - slow and apparently stalling. I have
> noticed that the cpu usage on the system remain high for minutes at a time.
> There is a second server with the same setup (but using sql7) that is for a
> separate company in the same network. The databases are similar in size and
> no one is having a problem with that system.
> I figure that if I have to rebuild or reinstall things, I should give the
> apps what they want (namely sql7).
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:A1B28A17-7343-4569-B8AF-0E2FE8D9E3C4@.microsoft.com...
> > Hi Bruce
> >
> > As they are querying the system catalogs directly then you can't easily
> > overcome this unless it is in a stored procedure where the code can be
> > changed. it looks like it is checking the user is in the dbo which could
> be
> > found by other methods.
> >
> > If this does not affect the functionality why would you want to revert
> back?
> >
> > John
> >
> >
> > "B. Horstmanshof" wrote:
> >
> > > Hi John.
> > >
> > > We are not paying support for this package. The pop-up error claims to
> be a
> > > connectivity error:
> > >
> > > Error # [1526]: Connectivity error: [Microsoft][ODBC SQL Server
> Driver][SQL
> > > Server]Invalid column name 'suid'.
> > >
> > > SQL Stmt:
> > > select name from sysusers where suid in (select suid master..sysusers
> where
> > > name='vamlogin') and name='dbo'
> > >
> > > They way it was explained to me is (as best I remember) that the name is
> > > used for something else or can't be used in SQL2000, but must exisit
> with
> > > this version of Accountmate. It was a while ago, and nobody seemed
> worried
> > > about it!
> > >
> > > Ideally the client would upgrade the software and move to 2003, but it
> is
> > > always a money issue - they would need to upgrade servers, o/s, sql and
> > > application, and they can't see the benefit of spending that kind of
> money!
> > >
> > > The backwards move would be to put the application on the platform it
> was
> > > supposed to be on, and see if the performance issues disappear.
> > >
> > > Bruce
> > >
> > >
> > > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > > news:A66A999D-2C70-4995-940A-387F58312CA4@.microsoft.com...
> > > > Hi
> > > >
> > > > You are downgrading to a product that will come to the end of it's
> life
> > > > sooner than the one you are on, which can't be good. I assume you are
> not
> > > > paying anything for the support of this package? If the login issue is
> > > your
> > > > only problem then I would try to find out why this happens rather than
> > > hoping
> > > > a downgrade will solve it. Do you get anything written into the SQL
> server
> > > > log or an specific error message/number?
> > > >
> > > > John
> > > >
> > > >
> > > >
> > > > "B. Horstmanshof" wrote:
> > > >
> > > > > I have a sql2000 server that I am contemplating downgrading to
> sql7...
> > > > >
> > > > > The scenario is this:
> > > > > The server was originally NT4, upgraded to Server2000.
> > > > > The server ran Accountmate using SQL7.
> > > > > SQL was upgraded to 2000.
> > > > >
> > > > > Turns out that the SQL2000 is not entirely compatible with the
> > > Accountmate -
> > > > > I don't have the exact reasons why. The application generates an
> error
> > > > > about a login name on startup. The user clicks ok, then continues
> > > without a
> > > > > problem.
> > > > > The client and Accountmate reps elected to leave as is. It has been
> > > about
> > > > > two years now!
> > > > >
> > > > > With the exception of adding data, no modifications have been made
> to
> > > the
> > > > > databases since.
> > > > >
> > > > > Is it possible to do the downgrade?
> > > > > What are the implications of doing?
> > > > > Where would I go to get specifics to the procedure?
> > > > >
> > > > > Thanks in advance for any help.
> > > > > Bruce.
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||Just backups (to disk) and optimization (reorganize pages and change free
space to 10%), both run through the Database maintenance plan on a daily
schedule.
The Application vendor takes care of that end - so I hope I answered the
question correctly!
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:56E40227-C36C-408C-970E-6EDDE317BB66@.microsoft.com...
> Hi Bruce,
> What sort of maintenance is is undertaken on this database?
> John
> "B. Horstmanshof" wrote:
> > The server is having problems - slow and apparently stalling. I have
> > noticed that the cpu usage on the system remain high for minutes at a
time.
> > There is a second server with the same setup (but using sql7) that is
for a
> > separate company in the same network. The databases are similar in size
and
> > no one is having a problem with that system.
> >
> > I figure that if I have to rebuild or reinstall things, I should give
the
> > apps what they want (namely sql7).
> >
> >
> > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > news:A1B28A17-7343-4569-B8AF-0E2FE8D9E3C4@.microsoft.com...
> > > Hi Bruce
> > >
> > > As they are querying the system catalogs directly then you can't
easily
> > > overcome this unless it is in a stored procedure where the code can be
> > > changed. it looks like it is checking the user is in the dbo which
could
> > be
> > > found by other methods.
> > >
> > > If this does not affect the functionality why would you want to revert
> > back?
> > >
> > > John
> > >
> > >
> > > "B. Horstmanshof" wrote:
> > >
> > > > Hi John.
> > > >
> > > > We are not paying support for this package. The pop-up error claims
to
> > be a
> > > > connectivity error:
> > > >
> > > > Error # [1526]: Connectivity error: [Microsoft][ODBC SQL Server
> > Driver][SQL
> > > > Server]Invalid column name 'suid'.
> > > >
> > > > SQL Stmt:
> > > > select name from sysusers where suid in (select suid
master..sysusers
> > where
> > > > name='vamlogin') and name='dbo'
> > > >
> > > > They way it was explained to me is (as best I remember) that the
name is
> > > > used for something else or can't be used in SQL2000, but must exisit
> > with
> > > > this version of Accountmate. It was a while ago, and nobody seemed
> > worried
> > > > about it!
> > > >
> > > > Ideally the client would upgrade the software and move to 2003, but
it
> > is
> > > > always a money issue - they would need to upgrade servers, o/s, sql
and
> > > > application, and they can't see the benefit of spending that kind of
> > money!
> > > >
> > > > The backwards move would be to put the application on the platform
it
> > was
> > > > supposed to be on, and see if the performance issues disappear.
> > > >
> > > > Bruce
> > > >
> > > >
> > > > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > > > news:A66A999D-2C70-4995-940A-387F58312CA4@.microsoft.com...
> > > > > Hi
> > > > >
> > > > > You are downgrading to a product that will come to the end of it's
> > life
> > > > > sooner than the one you are on, which can't be good. I assume you
are
> > not
> > > > > paying anything for the support of this package? If the login
issue is
> > > > your
> > > > > only problem then I would try to find out why this happens rather
than
> > > > hoping
> > > > > a downgrade will solve it. Do you get anything written into the
SQL
> > server
> > > > > log or an specific error message/number?
> > > > >
> > > > > John
> > > > >
> > > > >
> > > > >
> > > > > "B. Horstmanshof" wrote:
> > > > >
> > > > > > I have a sql2000 server that I am contemplating downgrading to
> > sql7...
> > > > > >
> > > > > > The scenario is this:
> > > > > > The server was originally NT4, upgraded to Server2000.
> > > > > > The server ran Accountmate using SQL7.
> > > > > > SQL was upgraded to 2000.
> > > > > >
> > > > > > Turns out that the SQL2000 is not entirely compatible with the
> > > > Accountmate -
> > > > > > I don't have the exact reasons why. The application generates
an
> > error
> > > > > > about a login name on startup. The user clicks ok, then
continues
> > > > without a
> > > > > > problem.
> > > > > > The client and Accountmate reps elected to leave as is. It has
been
> > > > about
> > > > > > two years now!
> > > > > >
> > > > > > With the exception of adding data, no modifications have been
made
> > to
> > > > the
> > > > > > databases since.
> > > > > >
> > > > > > Is it possible to do the downgrade?
> > > > > > What are the implications of doing?
> > > > > > Where would I go to get specifics to the procedure?
> > > > > >
> > > > > > Thanks in advance for any help.
> > > > > > Bruce.
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||Hi
If the jobs have not been failing then it sounds like it should be ok, have
you tried profiler to identify slow queries and missing indexes/statistics?
John
"B. Horstmanshof" wrote:
> Just backups (to disk) and optimization (reorganize pages and change free
> space to 10%), both run through the Database maintenance plan on a daily
> schedule.
> The Application vendor takes care of that end - so I hope I answered the
> question correctly!
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:56E40227-C36C-408C-970E-6EDDE317BB66@.microsoft.com...
> > Hi Bruce,
> >
> > What sort of maintenance is is undertaken on this database?
> >
> > John
> >
> > "B. Horstmanshof" wrote:
> >
> > > The server is having problems - slow and apparently stalling. I have
> > > noticed that the cpu usage on the system remain high for minutes at a
> time.
> > > There is a second server with the same setup (but using sql7) that is
> for a
> > > separate company in the same network. The databases are similar in size
> and
> > > no one is having a problem with that system.
> > >
> > > I figure that if I have to rebuild or reinstall things, I should give
> the
> > > apps what they want (namely sql7).
> > >
> > >
> > > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > > news:A1B28A17-7343-4569-B8AF-0E2FE8D9E3C4@.microsoft.com...
> > > > Hi Bruce
> > > >
> > > > As they are querying the system catalogs directly then you can't
> easily
> > > > overcome this unless it is in a stored procedure where the code can be
> > > > changed. it looks like it is checking the user is in the dbo which
> could
> > > be
> > > > found by other methods.
> > > >
> > > > If this does not affect the functionality why would you want to revert
> > > back?
> > > >
> > > > John
> > > >
> > > >
> > > > "B. Horstmanshof" wrote:
> > > >
> > > > > Hi John.
> > > > >
> > > > > We are not paying support for this package. The pop-up error claims
> to
> > > be a
> > > > > connectivity error:
> > > > >
> > > > > Error # [1526]: Connectivity error: [Microsoft][ODBC SQL Server
> > > Driver][SQL
> > > > > Server]Invalid column name 'suid'.
> > > > >
> > > > > SQL Stmt:
> > > > > select name from sysusers where suid in (select suid
> master..sysusers
> > > where
> > > > > name='vamlogin') and name='dbo'
> > > > >
> > > > > They way it was explained to me is (as best I remember) that the
> name is
> > > > > used for something else or can't be used in SQL2000, but must exisit
> > > with
> > > > > this version of Accountmate. It was a while ago, and nobody seemed
> > > worried
> > > > > about it!
> > > > >
> > > > > Ideally the client would upgrade the software and move to 2003, but
> it
> > > is
> > > > > always a money issue - they would need to upgrade servers, o/s, sql
> and
> > > > > application, and they can't see the benefit of spending that kind of
> > > money!
> > > > >
> > > > > The backwards move would be to put the application on the platform
> it
> > > was
> > > > > supposed to be on, and see if the performance issues disappear.
> > > > >
> > > > > Bruce
> > > > >
> > > > >
> > > > > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > > > > news:A66A999D-2C70-4995-940A-387F58312CA4@.microsoft.com...
> > > > > > Hi
> > > > > >
> > > > > > You are downgrading to a product that will come to the end of it's
> > > life
> > > > > > sooner than the one you are on, which can't be good. I assume you
> are
> > > not
> > > > > > paying anything for the support of this package? If the login
> issue is
> > > > > your
> > > > > > only problem then I would try to find out why this happens rather
> than
> > > > > hoping
> > > > > > a downgrade will solve it. Do you get anything written into the
> SQL
> > > server
> > > > > > log or an specific error message/number?
> > > > > >
> > > > > > John
> > > > > >
> > > > > >
> > > > > >
> > > > > > "B. Horstmanshof" wrote:
> > > > > >
> > > > > > > I have a sql2000 server that I am contemplating downgrading to
> > > sql7...
> > > > > > >
> > > > > > > The scenario is this:
> > > > > > > The server was originally NT4, upgraded to Server2000.
> > > > > > > The server ran Accountmate using SQL7.
> > > > > > > SQL was upgraded to 2000.
> > > > > > >
> > > > > > > Turns out that the SQL2000 is not entirely compatible with the
> > > > > Accountmate -
> > > > > > > I don't have the exact reasons why. The application generates
> an
> > > error
> > > > > > > about a login name on startup. The user clicks ok, then
> continues
> > > > > without a
> > > > > > > problem.
> > > > > > > The client and Accountmate reps elected to leave as is. It has
> been
> > > > > about
> > > > > > > two years now!
> > > > > > >
> > > > > > > With the exception of adding data, no modifications have been
> made
> > > to
> > > > > the
> > > > > > > databases since.
> > > > > > >
> > > > > > > Is it possible to do the downgrade?
> > > > > > > What are the implications of doing?
> > > > > > > Where would I go to get specifics to the procedure?
> > > > > > >
> > > > > > > Thanks in advance for any help.
> > > > > > > Bruce.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||John,
I found the problem... unrelated of course. Turns out that Surfcontrol
Spam filter is using a database on the server and that is what is stressing
the server! I can move it to a local msde datbase on the SurfControl
Server.
I appreciate your input - I would probably not found this so quickly without
it.
Many Thanks
Bruce
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:29CB601C-C569-4625-8E82-9C68CE01EEE1@.microsoft.com...
> Hi
> If the jobs have not been failing then it sounds like it should be ok,
have
> you tried profiler to identify slow queries and missing
indexes/statistics?
> John
> "B. Horstmanshof" wrote:
> > Just backups (to disk) and optimization (reorganize pages and change
free
> > space to 10%), both run through the Database maintenance plan on a daily
> > schedule.
> > The Application vendor takes care of that end - so I hope I answered the
> > question correctly!
> >
> > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > news:56E40227-C36C-408C-970E-6EDDE317BB66@.microsoft.com...
> > > Hi Bruce,
> > >
> > > What sort of maintenance is is undertaken on this database?
> > >
> > > John
> > >
> > > "B. Horstmanshof" wrote:
> > >
> > > > The server is having problems - slow and apparently stalling. I
have
> > > > noticed that the cpu usage on the system remain high for minutes at
a
> > time.
> > > > There is a second server with the same setup (but using sql7) that
is
> > for a
> > > > separate company in the same network. The databases are similar in
size
> > and
> > > > no one is having a problem with that system.
> > > >
> > > > I figure that if I have to rebuild or reinstall things, I should
give
> > the
> > > > apps what they want (namely sql7).
> > > >
> > > >
> > > > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > > > news:A1B28A17-7343-4569-B8AF-0E2FE8D9E3C4@.microsoft.com...
> > > > > Hi Bruce
> > > > >
> > > > > As they are querying the system catalogs directly then you can't
> > easily
> > > > > overcome this unless it is in a stored procedure where the code
can be
> > > > > changed. it looks like it is checking the user is in the dbo which
> > could
> > > > be
> > > > > found by other methods.
> > > > >
> > > > > If this does not affect the functionality why would you want to
revert
> > > > back?
> > > > >
> > > > > John
> > > > >
> > > > >
> > > > > "B. Horstmanshof" wrote:
> > > > >
> > > > > > Hi John.
> > > > > >
> > > > > > We are not paying support for this package. The pop-up error
claims
> > to
> > > > be a
> > > > > > connectivity error:
> > > > > >
> > > > > > Error # [1526]: Connectivity error: [Microsoft][ODBC SQL Server
> > > > Driver][SQL
> > > > > > Server]Invalid column name 'suid'.
> > > > > >
> > > > > > SQL Stmt:
> > > > > > select name from sysusers where suid in (select suid
> > master..sysusers
> > > > where
> > > > > > name='vamlogin') and name='dbo'
> > > > > >
> > > > > > They way it was explained to me is (as best I remember) that the
> > name is
> > > > > > used for something else or can't be used in SQL2000, but must
exisit
> > > > with
> > > > > > this version of Accountmate. It was a while ago, and nobody
seemed
> > > > worried
> > > > > > about it!
> > > > > >
> > > > > > Ideally the client would upgrade the software and move to 2003,
but
> > it
> > > > is
> > > > > > always a money issue - they would need to upgrade servers, o/s,
sql
> > and
> > > > > > application, and they can't see the benefit of spending that
kind of
> > > > money!
> > > > > >
> > > > > > The backwards move would be to put the application on the
platform
> > it
> > > > was
> > > > > > supposed to be on, and see if the performance issues disappear.
> > > > > >
> > > > > > Bruce
> > > > > >
> > > > > >
> > > > > > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > > > > > news:A66A999D-2C70-4995-940A-387F58312CA4@.microsoft.com...
> > > > > > > Hi
> > > > > > >
> > > > > > > You are downgrading to a product that will come to the end of
it's
> > > > life
> > > > > > > sooner than the one you are on, which can't be good. I assume
you
> > are
> > > > not
> > > > > > > paying anything for the support of this package? If the login
> > issue is
> > > > > > your
> > > > > > > only problem then I would try to find out why this happens
rather
> > than
> > > > > > hoping
> > > > > > > a downgrade will solve it. Do you get anything written into
the
> > SQL
> > > > server
> > > > > > > log or an specific error message/number?
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > "B. Horstmanshof" wrote:
> > > > > > >
> > > > > > > > I have a sql2000 server that I am contemplating downgrading
to
> > > > sql7...
> > > > > > > >
> > > > > > > > The scenario is this:
> > > > > > > > The server was originally NT4, upgraded to Server2000.
> > > > > > > > The server ran Accountmate using SQL7.
> > > > > > > > SQL was upgraded to 2000.
> > > > > > > >
> > > > > > > > Turns out that the SQL2000 is not entirely compatible with
the
> > > > > > Accountmate -
> > > > > > > > I don't have the exact reasons why. The application
generates
> > an
> > > > error
> > > > > > > > about a login name on startup. The user clicks ok, then
> > continues
> > > > > > without a
> > > > > > > > problem.
> > > > > > > > The client and Accountmate reps elected to leave as is. It
has
> > been
> > > > > > about
> > > > > > > > two years now!
> > > > > > > >
> > > > > > > > With the exception of adding data, no modifications have
been
> > made
> > > > to
> > > > > > the
> > > > > > > > databases since.
> > > > > > > >
> > > > > > > > Is it possible to do the downgrade?
> > > > > > > > What are the implications of doing?
> > > > > > > > Where would I go to get specifics to the procedure?
> > > > > > > >
> > > > > > > > Thanks in advance for any help.
> > > > > > > > Bruce.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >

Downgrade sql2000 to sql7

I have a sql2000 server that I am contemplating downgrading to sql7...
The scenario is this:
The server was originally NT4, upgraded to Server2000.
The server ran Accountmate using SQL7.
SQL was upgraded to 2000.
Turns out that the SQL2000 is not entirely compatible with the Accountmate -
I don't have the exact reasons why. The application generates an error
about a login name on startup. The user clicks ok, then continues without a
problem.
The client and Accountmate reps elected to leave as is. It has been about
two years now!
With the exception of adding data, no modifications have been made to the
databases since.
Is it possible to do the downgrade?
What are the implications of doing?
Where would I go to get specifics to the procedure?
Thanks in advance for any help.
Bruce.Hi
You are downgrading to a product that will come to the end of it's life
sooner than the one you are on, which can't be good. I assume you are not
paying anything for the support of this package? If the login issue is your
only problem then I would try to find out why this happens rather than hopin
g
a downgrade will solve it. Do you get anything written into the SQL server
log or an specific error message/number?
John
"B. Horstmanshof" wrote:

> I have a sql2000 server that I am contemplating downgrading to sql7...
> The scenario is this:
> The server was originally NT4, upgraded to Server2000.
> The server ran Accountmate using SQL7.
> SQL was upgraded to 2000.
> Turns out that the SQL2000 is not entirely compatible with the Accountmate
-
> I don't have the exact reasons why. The application generates an error
> about a login name on startup. The user clicks ok, then continues without
a
> problem.
> The client and Accountmate reps elected to leave as is. It has been about
> two years now!
> With the exception of adding data, no modifications have been made to the
> databases since.
> Is it possible to do the downgrade?
> What are the implications of doing?
> Where would I go to get specifics to the procedure?
> Thanks in advance for any help.
> Bruce.
>
>|||Hi John.
We are not paying support for this package. The pop-up error claims to be a
connectivity error:
Error # [1526]: Connectivity error: [Microsoft][ODBC SQL Server
Driver][SQL
Server]Invalid column name 'suid'.
SQL Stmt:
select name from sysusers where suid in (select suid master..sysusers where
name='vamlogin') and name='dbo'
They way it was explained to me is (as best I remember) that the name is
used for something else or can't be used in SQL2000, but must exisit with
this version of Accountmate. It was a while ago, and nobody seemed worried
about it!
Ideally the client would upgrade the software and move to 2003, but it is
always a money issue - they would need to upgrade servers, o/s, sql and
application, and they can't see the benefit of spending that kind of money!
The backwards move would be to put the application on the platform it was
supposed to be on, and see if the performance issues disappear.
Bruce
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:A66A999D-2C70-4995-940A-387F58312CA4@.microsoft.com...
> Hi
> You are downgrading to a product that will come to the end of it's life
> sooner than the one you are on, which can't be good. I assume you are not
> paying anything for the support of this package? If the login issue is
your
> only problem then I would try to find out why this happens rather than
hoping[vbcol=seagreen]
> a downgrade will solve it. Do you get anything written into the SQL server
> log or an specific error message/number?
> John
>
> "B. Horstmanshof" wrote:
>
Accountmate -[vbcol=seagreen]
without a[vbcol=seagreen]
about[vbcol=seagreen]
the[vbcol=seagreen]|||Hi Bruce
As they are querying the system catalogs directly then you can't easily
overcome this unless it is in a stored procedure where the code can be
changed. it looks like it is checking the user is in the dbo which could be
found by other methods.
If this does not affect the functionality why would you want to revert back?
John
"B. Horstmanshof" wrote:

> Hi John.
> We are not paying support for this package. The pop-up error claims to be
a
> connectivity error:
> Error # [1526]: Connectivity error: [Microsoft][ODBC SQL Serv
er Driver][SQL
> Server]Invalid column name 'suid'.
> SQL Stmt:
> select name from sysusers where suid in (select suid master..sysusers wher
e
> name='vamlogin') and name='dbo'
> They way it was explained to me is (as best I remember) that the name is
> used for something else or can't be used in SQL2000, but must exisit with
> this version of Accountmate. It was a while ago, and nobody seemed worrie
d
> about it!
> Ideally the client would upgrade the software and move to 2003, but it is
> always a money issue - they would need to upgrade servers, o/s, sql and
> application, and they can't see the benefit of spending that kind of money
!
> The backwards move would be to put the application on the platform it was
> supposed to be on, and see if the performance issues disappear.
> Bruce
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:A66A999D-2C70-4995-940A-387F58312CA4@.microsoft.com...
> your
> hoping
> Accountmate -
> without a
> about
> the
>
>|||The server is having problems - slow and apparently stalling. I have
noticed that the cpu usage on the system remain high for minutes at a time.
There is a second server with the same setup (but using sql7) that is for a
separate company in the same network. The databases are similar in size and
no one is having a problem with that system.
I figure that if I have to rebuild or reinstall things, I should give the
apps what they want (namely sql7).
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:A1B28A17-7343-4569-B8AF-0E2FE8D9E3C4@.microsoft.com...
> Hi Bruce
> As they are querying the system catalogs directly then you can't easily
> overcome this unless it is in a stored procedure where the code can be
> changed. it looks like it is checking the user is in the dbo which could
be
> found by other methods.
> If this does not affect the functionality why would you want to revert
back?[vbcol=seagreen]
> John
>
> "B. Horstmanshof" wrote:
>
be a[vbcol=seagreen]
Driver][SQL[vbcol=seagreen]
where[vbcol=seagreen]
with[vbcol=seagreen]
worried[vbcol=seagreen]
is[vbcol=seagreen]
money![vbcol=seagreen]
was[vbcol=seagreen]
life[vbcol=seagreen]
not[vbcol=seagreen]
server[vbcol=seagreen]
sql7...[vbcol=seagreen]
error[vbcol=seagreen]
to[vbcol=seagreen]|||Hi Bruce,
What sort of maintenance is is undertaken on this database?
John
"B. Horstmanshof" wrote:

> The server is having problems - slow and apparently stalling. I have
> noticed that the cpu usage on the system remain high for minutes at a time
.
> There is a second server with the same setup (but using sql7) that is for
a
> separate company in the same network. The databases are similar in size a
nd
> no one is having a problem with that system.
> I figure that if I have to rebuild or reinstall things, I should give the
> apps what they want (namely sql7).
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:A1B28A17-7343-4569-B8AF-0E2FE8D9E3C4@.microsoft.com...
> be
> back?
> be a
> Driver][SQL
> where
> with
> worried
> is
> money!
> was
> life
> not
> server
> sql7...
> error
> to
>
>|||Just backups (to disk) and optimization (reorganize pages and change free
space to 10%), both run through the Database maintenance plan on a daily
schedule.
The Application vendor takes care of that end - so I hope I answered the
question correctly!
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:56E40227-C36C-408C-970E-6EDDE317BB66@.microsoft.com...[vbcol=seagreen]
> Hi Bruce,
> What sort of maintenance is is undertaken on this database?
> John
> "B. Horstmanshof" wrote:
>
time.[vbcol=seagreen]
for a[vbcol=seagreen]
and[vbcol=seagreen]
the[vbcol=seagreen]
easily[vbcol=seagreen]
could[vbcol=seagreen]
to[vbcol=seagreen]
master..sysusers[vbcol=seagreen]
name is[vbcol=seagreen]
it[vbcol=seagreen]
and[vbcol=seagreen]
it[vbcol=seagreen]
are[vbcol=seagreen]
issue is[vbcol=seagreen]
than[vbcol=seagreen]
SQL[vbcol=seagreen]
an[vbcol=seagreen]
continues[vbcol=seagreen]
been[vbcol=seagreen]
made[vbcol=seagreen]|||Hi
If the jobs have not been failing then it sounds like it should be ok, have
you tried profiler to identify slow queries and missing indexes/statistics?
John
"B. Horstmanshof" wrote:

> Just backups (to disk) and optimization (reorganize pages and change free
> space to 10%), both run through the Database maintenance plan on a daily
> schedule.
> The Application vendor takes care of that end - so I hope I answered the
> question correctly!
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:56E40227-C36C-408C-970E-6EDDE317BB66@.microsoft.com...
> time.
> for a
> and
> the
> easily
> could
> to
> master..sysusers
> name is
> it
> and
> it
> are
> issue is
> than
> SQL
> an
> continues
> been
> made
>
>|||John,
I found the problem... unrelated of course. Turns out that Surfcontrol
Spam filter is using a database on the server and that is what is stressing
the server! I can move it to a local msde datbase on the SurfControl
Server.
I appreciate your input - I would probably not found this so quickly without
it.
Many Thanks
Bruce
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:29CB601C-C569-4625-8E82-9C68CE01EEE1@.microsoft.com...
> Hi
> If the jobs have not been failing then it sounds like it should be ok,
have
> you tried profiler to identify slow queries and missing
indexes/statistics?[vbcol=seagreen]
> John
> "B. Horstmanshof" wrote:
>
free[vbcol=seagreen]
have[vbcol=seagreen]
a[vbcol=seagreen]
is[vbcol=seagreen]
size[vbcol=seagreen]
give[vbcol=seagreen]
can be[vbcol=seagreen]
revert[vbcol=seagreen]
claims[vbcol=seagreen]
exisit[vbcol=seagreen]
seemed[vbcol=seagreen]
but[vbcol=seagreen]
sql[vbcol=seagreen]
kind of[vbcol=seagreen]
platform[vbcol=seagreen]
it's[vbcol=seagreen]
you[vbcol=seagreen]
rather[vbcol=seagreen]
the[vbcol=seagreen]
to[vbcol=seagreen]
the[vbcol=seagreen]
generates[vbcol=seagreen]
has[vbcol=seagreen]
been[vbcol=seagreen]