Can I Created a BPA 'Job'

Can I created a job that I can send to my Service Delivery group to run on the Production servers? I'm a developer and don't WANT access to PROD, but I want BPA run against PROD. I'd like to have them install BPA and them send them a 'package' to run. Is
this available with BPA?
Thanks,
Maybe not exactly what you want, but there's a way you can get close.
Install BPA, which creates the repository. In it, create a best practice
group that scans things the way you want. You should register the servers
from production, or register them as (local).
Have your production team install BPA (they will have to create a repository
but it can be discarded) and then ask them to run bpa (likely the command
line version bpacmd.exe) pointing at your repository database. If they do
that, they'll have to execute the best practice group that you created.
- Christian
"B.W." <bw.lightsey@.tetrapak.com> wrote in message
news:611E0DF9-C69E-4EF6-AA6B-0E390C3430A8@.microsoft.com...
> Can I created a job that I can send to my Service Delivery group to run on
the Production servers? I'm a developer and don't WANT access to PROD, but I
want BPA run against PROD. I'd like to have them install BPA and them send
them a 'package' to run. Is this available with BPA?
> Thanks,
>
sql

Can I apply this hot fix to solve SqlBulkCopy issue?

Hi,
Our production SQL databaseâ' located on SQL Server 2005 (SP2) with 3161
version. When we use the SqlBulkCopy, the following error occurs:
System.Data.SqlClient.SqlException: The incoming tabular data stream (TDS)
protocol stream is incorrect. The TDS headers contained errors.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception,
Boolean breakConnection)
We searched on web site and found this
http://support.microsoft.com/kb/913177/en-us article.
Now, I want know this hot fix version is higher than 3161 or lower because
we are currently on 3161 version.
Regards,
ChenI don't think this fix affects SQL Server versioning, and doesn't seem to
have anything to do with specific SQL Server hotfixes. So, it is probably
worth a try.
There are also later builds available for SQL Server... you may want to
check cumulative updates 1 - 7 for any mention of the issue you are seeing.
The best part is, you no longer have to call CSS to get one of these
updates.
http://sqlblog.com/blogs/aaron_bertrand/archive/2008/04/25/don-t-want-to-call-css-pss-to-get-a-cumjulative-update-you-don-t-have-to.aspx
"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:34AB0521-F9E8-4249-B77C-341FDA1DA921@.microsoft.com...
> Hi,
> Our production SQL databaseâ' located on SQL Server 2005 (SP2) with 3161
> version. When we use the SqlBulkCopy, the following error occurs:
> System.Data.SqlClient.SqlException: The incoming tabular data stream (TDS)
> protocol stream is incorrect. The TDS headers contained errors.
> at System.Data.SqlClient.SqlConnection.OnError(SqlException exception,
> Boolean breakConnection)
> We searched on web site and found this
> http://support.microsoft.com/kb/913177/en-us article.
> Now, I want know this hot fix version is higher than 3161 or lower because
> we are currently on 3161 version.
> Regards,
> Chen|||Thank you very much!
"Aaron Bertrand [SQL Server MVP]" wrote:
> I don't think this fix affects SQL Server versioning, and doesn't seem to
> have anything to do with specific SQL Server hotfixes. So, it is probably
> worth a try.
> There are also later builds available for SQL Server... you may want to
> check cumulative updates 1 - 7 for any mention of the issue you are seeing.
> The best part is, you no longer have to call CSS to get one of these
> updates.
> http://sqlblog.com/blogs/aaron_bertrand/archive/2008/04/25/don-t-want-to-call-css-pss-to-get-a-cumjulative-update-you-don-t-have-to.aspx
>
>
>
> "Chen" <Chen@.discussions.microsoft.com> wrote in message
> news:34AB0521-F9E8-4249-B77C-341FDA1DA921@.microsoft.com...
> > Hi,
> > Our production SQL databaseâ' located on SQL Server 2005 (SP2) with 3161
> > version. When we use the SqlBulkCopy, the following error occurs:
> >
> > System.Data.SqlClient.SqlException: The incoming tabular data stream (TDS)
> > protocol stream is incorrect. The TDS headers contained errors.
> > at System.Data.SqlClient.SqlConnection.OnError(SqlException exception,
> > Boolean breakConnection)
> >
> > We searched on web site and found this
> > http://support.microsoft.com/kb/913177/en-us article.
> >
> > Now, I want know this hot fix version is higher than 3161 or lower because
> > we are currently on 3161 version.
> >
> > Regards,
> > Chen
>

Can BCP Handle Leap Day: 2/29/08 ?

I have a production job that is killing BCP... If I change the dates to
2/28/08, the file processes just fine. Here is the error message ... is
this a known issue? Is there a fix for this?
#@. Row 11366, Column 2: Invalid date format @.#
1/21/08 2/29/08 1 0073210002300 0 3.68 12
#@. Row 24909, Column 2: Invalid date format @.#
1/21/08 2/29/08 4 0073210002300 0 3.68 12
#@. Row 38452, Column 2: Invalid date format @.#
1/21/08 2/29/08 7 0073210002300 0 3.68 12
#@. Row 51995, Column 2: Invalid date format @.#
1/21/08 2/29/08 14 0073210002300 0 3.68 12
#@. Row 65538, Column 2: Invalid date format @.#
Thanks!
Greg,
I am sure that bcp is simply using the SQL Server engine, so I would expect
it to 'know'. When I tested the following file all rows worked.
2/29/08
2/28/08
2/29/2008
2/28/2008
If the date was invalid, you would get the message that you show. I get the
errorw when I include a row with:
2/30/2008
So, one possibility is that your format file (or the format of your file) is
the problem. Are you using a format file or are you depending on tabs and
column order? (The latter is fine when it works, of course, but sometimes
you need a format file to control things more. See:
http://support.microsoft.com/kb/67409 and look "format files" in the SQL
Server Book Online for some examples.)
RLF
"greg may" <gregory_may [at] yahoo [dot] com> wrote in message
news:%233wz4JyvHHA.736@.TK2MSFTNGP06.phx.gbl...
>I have a production job that is killing BCP... If I change the dates to
>2/28/08, the file processes just fine. Here is the error message ... is
>this a known issue? Is there a fix for this?
> #@. Row 11366, Column 2: Invalid date format @.#
> 1/21/08 2/29/08 1 0073210002300 0 3.68 12
> #@. Row 24909, Column 2: Invalid date format @.#
> 1/21/08 2/29/08 4 0073210002300 0 3.68 12
> #@. Row 38452, Column 2: Invalid date format @.#
> 1/21/08 2/29/08 7 0073210002300 0 3.68 12
> #@. Row 51995, Column 2: Invalid date format @.#
> 1/21/08 2/29/08 14 0073210002300 0 3.68 12
> #@. Row 65538, Column 2: Invalid date format @.#
>
>
> Thanks!
>
|||Thanks Russell for your feedback. I will have to set up some more tests to
track this down further.
We are not using a format file in this case. Its using an implicid
conversion as the table structure and the field lay outs are an exact match
(Using Pipe delimiters) ... this may be part of what is causing the issue?
In this case, the destination table is using a SmallDateTime.
I will see if I can reproduce the problem with only the above conditions.
g.
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:uUKHnIzvHHA.4244@.TK2MSFTNGP04.phx.gbl...
> Greg,
> I am sure that bcp is simply using the SQL Server engine, so I would
> expect it to 'know'. When I tested the following file all rows worked.
> 2/29/08
> 2/28/08
> 2/29/2008
> 2/28/2008
> If the date was invalid, you would get the message that you show. I get
> the errorw when I include a row with:
> 2/30/2008
> So, one possibility is that your format file (or the format of your file)
> is the problem. Are you using a format file or are you depending on tabs
> and column order? (The latter is fine when it works, of course, but
> sometimes you need a format file to control things more. See:
> http://support.microsoft.com/kb/67409 and look "format files" in the SQL
> Server Book Online for some examples.)
> RLF
> "greg may" <gregory_may [at] yahoo [dot] com> wrote in message
> news:%233wz4JyvHHA.736@.TK2MSFTNGP06.phx.gbl...
>

Can aspnetdb.mdf be moved from development to production machine?

1.) Can an aspnetdb.mdf database be configured and setup on one server and then be moved to a production server or is there something machine specific that keeps this from being possible?
2.) Is putting this file in the app_data folder something that is used only for SQL 2005 or SQL express? I had to set up a connection string in my SQL 2000 installation to get the connection to work.

Thanks for any input!

Colelaus

aspnetdb.mdf is the default sql express database created, if you want to move it onto production, your production server has to install sql express and reference it in your connection string|||

I'm using aspnetdb.mdf as my security database but not SQL Express due to llimitations on the server. I guess my question is really is there anything that is generated in the database when setting up security that is machine specific that would keep the database from being moved from one machine to another?

If it is machine specific, it would require as you referenced, me to recreate on the production server and reset all the users again.

Colelaus

|||

Hi Colelaus,

If your production server provides SQL server other editions than the Express edition, you will need to have the .mdf database files attach to server manually, since other edtions of SQL server does not support attaching database files automatically at runtime.

Also, you will need to modify your connection string and make it look like "Data Source=ServerName\InstanceName;Initial Catelog=DatabaseName". It points to a database on server instead of a .mdf file.For other information, you will need to contact the hosting service.

The tool you may use : Aspnet_regsql.exe ( More details about the tool, pls visit http://msdn2.microsoft.com/en-us/library/ms229862(VS.80).aspx )

Thanks.

|||

Thanks. That is exactly the info I needed.

Colelaus

Can a DTS package be scripted or transferred to another server?

I have production SQL Server database that must be moved to a new
machine. There is a fairly complex DTS package on the original server
that is used to handle the weekly updates to the database.

Is there a way to export this DTS package in order to set it up on the
new machine as well?

Best Regards,

Warren Wright
Scorex Development Teamwarren.wright@.us.scorex.com (Warren Wright) wrote in message news:<8497c269.0307291200.68fe227b@.posting.google.com>...
> I have production SQL Server database that must be moved to a new
> machine. There is a fairly complex DTS package on the original server
> that is used to handle the weekly updates to the database.
> Is there a way to export this DTS package in order to set it up on the
> new machine as well?
> Best Regards,
> Warren Wright
> Scorex Development Team

http://www.sqldts.com/default.aspx?6,105,204,0,1

The June issue of SQL Server magazine (http://www.sqlmag.com) had a
good article on making DTS packages portable between servers.

Simon|||warren.wright@.us.scorex.com (Warren Wright) wrote in message news:<8497c269.0307291200.68fe227b@.posting.google.com>...
> I have production SQL Server database that must be moved to a new
> machine. There is a fairly complex DTS package on the original server
> that is used to handle the weekly updates to the database.
> Is there a way to export this DTS package in order to set it up on the
> new machine as well?
> Best Regards,
> Warren Wright
> Scorex Development Team

You can, when designing the DTS Package, select "Save As..." and
change the "location" to a structured storage file. You can then
import this file onto your production server. If you scripted all
your local connections as "(local)", then this should be the end of
the story, if not, you'll need to open it and change your local
connections to the production server.

Hope this helps

Hodge|||Warren

Try this link.

http://www.sqldts.com/default.aspx?6,105,204,0,1

Hope that helps

John

Calling VBA functions from SQL

I have a rather complex function (part of a production planning engine) that is written in VBA, and is part of my front end app. I'd like to be able to somehow call this function from either a sproc or DTS package in SQL. Is this possible, or am I going to have to convert the function to a SQL sproc (ugh)?Plop the VBA script into an Active-X task within a DTS package, and you should be "good to go". Another choice that folks often overlook is to make the VBA an ActiveX Script step in a SQL Agent job.

-PatP|||Thanks, Pat.

I was thinking along those lines, so I did a little more research while waiting for an answer. It appears that VBScript (and ActiveX??) doesn't like arrays, especially the dynamic variety. I think what I'm trying to do may be misuse of a sproc, but since I want the task to run as part of a rather large string of scheduled tasks, I'm stuck with converting it.