Migrating from Enterprise to SQL Server 2000 Standard

We are migrating a browser based application developed
with the Enterprise version to a server running the
standard edition. There will be some development on the
standard version before a new vresion of the application
is deployed. Can anyone help me to understand what
issues/problems we should look out for?Since most of the difference between Standard Edition and Enterprise Edition
involves scalability and availability features (>4 processors, large memory
support, clusters) there generally will be no problems migrating
applications from Enterprise to Standard. The few small gotchas include
Transparent Materialized Views and Distributed Partitioned Views, both of
which are only included in Enterprise Edition. (For completeness, Analysis
Services has some similar differences between Standard and Enterprise). If
you have not used these few scalability-related features then you will not
notice application level differences between these editions.
See "Features Supported by the Editions of SQL Server 2000" in Books Online.
--
Hal Berenson, SQL Server MVP
True Mountain Group LLC
"rez" <rezam@.go.com> wrote in message
news:039601c37bc5$bda02a30$a401280a@.phx.gbl...
> We are migrating a browser based application developed
> with the Enterprise version to a server running the
> standard edition. There will be some development on the
> standard version before a new vresion of the application
> is deployed. Can anyone help me to understand what
> issues/problems we should look out for?

Migrating From Access 2000 To SQl Server 2000

Hi,

I have developed an application using VB 6 (SP 5), MS Access 2000 and
Crystal Reports 9. I migrated from from access to SQl Server 2000.
This wasn't a problem as i could import all the tables to SQL Server.
Also, i could make VB6 talk to SQl Server.

The problem arsies when i run my application. The sql syntax for
access seems to be different than that for SQL Server. A simple
example being: In access boolean datatype is true/false ,whereas in
SQL Server the boolean equivalent is bit (numerical 1 or 0). These
kind of issues are causing problems and most queries don't run.

Would i need to go and change all the queries in accordance with SQl
Server syntax ,which would be very time consuming or is there any
function which will convert the access datatype into its equivalent
SQl Server datatype??

Any input/thoughts/suggestions would be appreciated.

Thanks
JatinThere is a big problem with ODBC JET Linked tables when it comes to boolean
fields in Access that get turned into BIT fields in SQL Server.

Basically, JET thinks of boolean TRUE as (-1) where SQL thinks of it as (1).
The ODBC driver switches the values for you in Access, so that when you look at
the table it shows (-1)...but if you look at the table in SQL Server it says
(1).

The bottom line is that the ODBC driver does NOT understand what TRUE or FALSE
means, so the short answer is YES, you have to change all of those refrences to
(-1) or (0) respectively.

The standard, quick answer to this problem is to use a find/replace tool (in
NOTEPAD) to change all

= TRUE

to

= -1

and = FALSE

to

= 0

WARNING: This is only true for JET-based ODBC queries. If you create a view on
SQL Server, you'll have to use = 1 for TRUE!!!!

For that reason, I normally use =0 for FALSE, and <>0 for TRUE!!! That way, it
always works.

Another option is to change the BIT datatype on SQL Server to INT
(integer)...that way a (-1) WILL BE STORED by the ODBC driver, and it'll be
consistent.

Hope this helps!

Migrate

I have developed a web application using MSDE. I do not have sql 2000. I now have to transfer this database to an asp host.
Is there a DTS package or osql commands that I can export the entire database sp and all to a sql script file.

Regards
S(:You can create scripts for all of the database objects (tables, view, sprocs, etc.) but I don't believe you can create scripts for the data too. You can use DTS to copy the data, however, after you create the objects.

I haven't tried this with MSDE but with Sql Server databases you can detach them from your local database and physically copy the database files to the remote destination and then re-attach them there. The database has to be compatible with where you are attaching it and whether it considers MSDE files compatible is the question.

Microsoft.Reporting.WebForms.ReportViewer does not contain a definition for Reset

Hi everyone I developed a web form with a report viewer. I change the report datasource and report path based on user input. Before i do anything on the report i first reset it with this line:

rvWaitTime.Reset();

And then set the parameters, datasources, etc. It works fine on my dev machine: Windows Vista with .NET 2.0 installed (.NET 3.0 is installed as well). When I move the code to the production box: Windows Server 2003 with .NET 2.0 and 3.0 installed i get this error:

'Microsoft.Reporting.WebForms.ReportViewer' does not contain a definition for 'Reset'

and of course it fails on the line of code mentioned above.

Any ideas?

Who would have thought that you needed a seperate installation for a control that comes built in with VS 2005? I finally solved the problem. I needed to install theMicrosoft Report Viewer Redistributable 2005 SP1 (Full Installation) on my server and now everything works like a charm!