Development Direction

I'm hoping that someone can suggest a direction for me to get started to
update a current application that I built several years ago. I want to move
the following application to our organization's intranet and will need to get
training in the best method to achieve this. I am versed in Office VBA and
VB 6.0 but have not moved into the .NET arena yet.
The application in question uses SQL Server 2000 as a back end and Access
2000 for the front end. Users basically select options on an Access form
that is used in a pass-through query to SQL Server. The query logs into the
server runs the query and returns the data, not to Access, but to an Excel
spreadsheet. I did this at the request of the users and they have been very
happy with it for many years.
The problem lies when users get new machines or have their machines
re-imaged and our computer support group has to re-install yet another
application. It would be great if I could figure out a way to build a
web-enabled version of this application and it has been beyond the scope of
my knowledge for some time now. I would really appreciate any suggestions
you might have or if you feel I need to direct this question to a different
newsgroup. Please advise. Thank you... AlIf you are able to use Reporting Services this is pretty easy to do what you
want. You have the queries designed. They can use the portal that ships with
RS (Report Manager). Select the parameters and view the report and then
export to Excel. If you had your own web page you could go directly to Excel
but since you don't want to be creating your own web app my suggestion
totally uses the feature of RS. You design and deploy the report and there
you are BUT the problem is going to be the administration. It requires
having RS server somewhere that you can deploy against.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Al" <Al@.discussions.microsoft.com> wrote in message
news:FD312550-1020-4D2B-B913-AE40BB5A28BC@.microsoft.com...
> I'm hoping that someone can suggest a direction for me to get started to
> update a current application that I built several years ago. I want to
> move
> the following application to our organization's intranet and will need to
> get
> training in the best method to achieve this. I am versed in Office VBA
> and
> VB 6.0 but have not moved into the .NET arena yet.
> The application in question uses SQL Server 2000 as a back end and Access
> 2000 for the front end. Users basically select options on an Access form
> that is used in a pass-through query to SQL Server. The query logs into
> the
> server runs the query and returns the data, not to Access, but to an Excel
> spreadsheet. I did this at the request of the users and they have been
> very
> happy with it for many years.
> The problem lies when users get new machines or have their machines
> re-imaged and our computer support group has to re-install yet another
> application. It would be great if I could figure out a way to build a
> web-enabled version of this application and it has been beyond the scope
> of
> my knowledge for some time now. I would really appreciate any suggestions
> you might have or if you feel I need to direct this question to a
> different
> newsgroup. Please advise. Thank you... Al

Dev to Prod

I am building a new database in a Development environment (tables, stored pr
ocedures...etc.). Can you suggest reliable ways to move it to Production wh
en the project is ready to move to prod. This is kind a new to me and I am
wondering what tools would
be helpful.
ThanksIt depends on what you want to move. I have elaborated on different tools to
generate scripts, some with data on below line:
http://www.karaszi.com/sqlserver/in...rate_script.asp
Also, backup/restore or detach/attach is an option, but you need to handle
orphaned users after.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Niles" <anonymous@.discussions.microsoft.com> wrote in message
news:C073E2DC-DAD3-4516-B304-112EB810EF31@.microsoft.com...
> I am building a new database in a Development environment (tables, stored
procedures...etc.). Can you suggest reliable ways to move it to Production
when the project is ready to move to prod. This is kind a new to me and I
am wondering what tools would be helpful.
> Thanks

Determining Proper Maxdop, Threshold and Worker Threads.

Hey guys - I am wondering if anyone can suggest some good literature on determining the proper Maxdop, Parallel Threshold, and # of worker threads to run.

We were in the MS Lab out in San Jose last week benchmarking our app against SQL 2k and SQL 2k5, and it seems that CXPackets were killing us in 2k5 (running against 4 dc opterons). Turning off Maxdop helped, but we have a pretty wide range of queries in our application - stuff ranging from a couple of milliseconds to an occasional 10k ms. I would like to use maxdop, but I am wondering how to approach finding the ideal threshold (other than just benchmarking it to death).

Also, same kind of question on worker threads - is there a methodology for finding the right setting for my environment, or is it pin the tail on the donkey?

Our app typically runs against 16 or 32 way boxes with tons of memory.

Hi,

There is a rule of thumb concerning the worker threads in the BOL of SQL Server 2005.
In SQL Server 2005 this is 'self tuning' by default.

I don't know of any 'wonder' formulas to determine the other settings (except benchmarking it to death) :-)
If I do find something I'll let you know.

Kr