DBA Administration db

HI, I would like to set up a dba admin database on each of the instances that I have. Is there any recommended standard format for this database?

Thanks

It would be totally dependent upon how you plan to use it. There are just too many variables.

DBA Administration db

HI, I would like to set up a dba admin database on each of the instances that I have. Is there any recommended standard format for this database?

Thanks

It would be totally dependent upon how you plan to use it. There are just too many variables.

DB2OLEDB for SQL Server 2005 Standard Edition

The Microsoft OLEDB provider for DB2 (DB2OLEDB) is available in the "Feature Pack for SQL Server 2005 – April 2006." The installation routine, however, will only install on the enterprise edition or the developer edition. Is the DB2OLEDB provider not available for SQL Server 2005 standard edition?

I just went through the README.htm that comes with the installation of DB2OLEDB and it explicitly states that:

The Microsoft OLE DB Provider for DB2 is for use exclusively with Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Developer Edition and Microsoft SQL Server 2005 Evaluation Copy.

So I believe the behaviour you are seeing is expected.

Thanks

Waseem Basheer

|||

If you want a Microsoft OLEDB provider for DB2 you have to install client tools from Host Integration Server. You can choose it under custom install.

i

DB2OLEDB for SQL Server 2005 Standard Edition

The Microsoft OLEDB provider for DB2 (DB2OLEDB) is available in the "Feature Pack for SQL Server 2005 – April 2006." The installation routine, however, will only install on the enterprise edition or the developer edition. Is the DB2OLEDB provider not available for SQL Server 2005 standard edition?

I just went through the README.htm that comes with the installation of DB2OLEDB and it explicitly states that:

The Microsoft OLE DB Provider for DB2 is for use exclusively with Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Developer Edition and Microsoft SQL Server 2005 Evaluation Copy.

So I believe the behaviour you are seeing is expected.

Thanks

Waseem Basheer

|||

If you want a Microsoft OLEDB provider for DB2 you have to install client tools from Host Integration Server. You can choose it under custom install.

i

DB2 and Report Builder

I have successfully deployed a standard Report (i.e. non Report Builder) to our Report Server using a Shared Data Source to an iSeries Access for Windows Driver. The Data Source has the following properties:

Type :OLEDB

Connection String : Provider=IBMDA400.DataSource.1;Data Source=AA;Initial Catalog=AA;Default Collection=MITDTA;Catalog Library List=MITDTA,MVXBDTA

The Report works perfectly using this connection.

However when I try to run a Report Builder Report based on a Report Builder Model that uses this same shared connection I get the following error:

An attempt has been made to use a data extension 'OLEDB' that is not registered for this report server.

-

Cannot create command for data source 'dataSource1'.

-

An error has occurred during report processing.

Any ideas?

I'm not sure how you created a report model based on an OLEDB connection. In the RTM release only SQL Server 2000/2005 and Analysis Services 2005 are supported. We are adding Oracle support in SP2, but we do not have DB2 support yet.

|||

OK I hadn't realised DB2 was not yet supported ...

I managed to create a Data Source View based on the MS OLE DB Provider for DB2 (not in fact the iSeries Driver I mentioned above) and explored the data successfully from VS. I then created a .smdl file (not from the Autogenerate command) and deployed this to the Server successfully. If this was not a supported Provider then I guess I would have expected to be told at the Deploy stage and the Deploy would have failed..

No problem I'll find another solution. Cheers.

|||

hi Bob

I'm using SQL Express (SSE) with the Reports Services and I'm getting this same error. Is OLEDB supported now?

I've noticed that in the rsreportserver.config file, there is an entry under <Configuration><Extensions><Data> as follows:

<Extension Name="OLEDB" Type="Microsoft.ReportingServices.DataExtensions.OleDbConnectionWrapper,Microsoft.ReportingServices.DataExtensions"/>

Any ideas?

Cheers

Steve

DB2 and Report Builder

I have successfully deployed a standard Report (i.e. non Report Builder) to our Report Server using a Shared Data Source to an iSeries Access for Windows Driver. The Data Source has the following properties:

Type : OLEDB

Connection String : Provider=IBMDA400.DataSource.1;Data Source=AA;Initial Catalog=AA;Default Collection=MITDTA;Catalog Library List=MITDTA,MVXBDTA

The Report works perfectly using this connection.

However when I try to run a Report Builder Report based on a Report Builder Model that uses this same shared connection I get the following error:

An attempt has been made to use a data extension 'OLEDB' that is not registered for this report server.

-

Cannot create command for data source 'dataSource1'.

-

An error has occurred during report processing.

Any ideas?

I'm not sure how you created a report model based on an OLEDB connection. In the RTM release only SQL Server 2000/2005 and Analysis Services 2005 are supported. We are adding Oracle support in SP2, but we do not have DB2 support yet.

|||

OK I hadn't realised DB2 was not yet supported ...

I managed to create a Data Source View based on the MS OLE DB Provider for DB2 (not in fact the iSeries Driver I mentioned above) and explored the data successfully from VS. I then created a .smdl file (not from the Autogenerate command) and deployed this to the Server successfully. If this was not a supported Provider then I guess I would have expected to be told at the Deploy stage and the Deploy would have failed..

No problem I'll find another solution. Cheers.

DB2 and Report Builder

I have successfully deployed a standard Report (i.e. non Report Builder) to our Report Server using a Shared Data Source to an iSeries Access for Windows Driver. The Data Source has the following properties:

Type : OLEDB

Connection String : Provider=IBMDA400.DataSource.1;Data Source=AA;Initial Catalog=AA;Default Collection=MITDTA;Catalog Library List=MITDTA,MVXBDTA

The Report works perfectly using this connection.

However when I try to run a Report Builder Report based on a Report Builder Model that uses this same shared connection I get the following error:

An attempt has been made to use a data extension 'OLEDB' that is not registered for this report server.

-

Cannot create command for data source 'dataSource1'.

-

An error has occurred during report processing.

Any ideas?

I'm not sure how you created a report model based on an OLEDB connection. In the RTM release only SQL Server 2000/2005 and Analysis Services 2005 are supported. We are adding Oracle support in SP2, but we do not have DB2 support yet.

|||

OK I hadn't realised DB2 was not yet supported ...

I managed to create a Data Source View based on the MS OLE DB Provider for DB2 (not in fact the iSeries Driver I mentioned above) and explored the data successfully from VS. I then created a .smdl file (not from the Autogenerate command) and deployed this to the Server successfully. If this was not a supported Provider then I guess I would have expected to be told at the Deploy stage and the Deploy would have failed..

No problem I'll find another solution. Cheers.

|||

hi Bob

I'm using SQL Express (SSE) with the Reports Services and I'm getting this same error. Is OLEDB supported now?

I've noticed that in the rsreportserver.config file, there is an entry under <Configuration><Extensions><Data> as follows:

<Extension Name="OLEDB" Type="Microsoft.ReportingServices.DataExtensions.OleDbConnectionWrapper,Microsoft.ReportingServices.DataExtensions"/>

Any ideas?

Cheers

Steve

DB Server: IDE vs. SCSI - What are the advantages?

Hi,

We are going to be setting up an e-commerce web site that runs on SQL Server 2000 standard and we need to purchase a database server and are not sure whether we will have a use for SCSI hard drives or can stick with IDE RAID.

The server will just run SQL SERVER 2000, nothing else. There are no images, or anything like that being stored in the database or on the server, but credit card transactions, and orders will be taking place so we want that to be efficient.

Can someone give a good explanation of which (IDE or RAID) would server us better and why?

Thank you,

MarkMark, you haven't given nearly enogh info to make an analysis of any kind but I can offer some clarification...

First you definatly want some kind of RAID technology. This can give you drive redundency and depending on he kind of card purchased, some flexability in how you partition your drives.

IDE vs SCSI. It is true you can save some money by going IDE but the technology hasn't been around long enough. If you absolutly had to cut costs to the bone and purchased IDE then I would watch the error logs like a hawk for any problems that might arrise.
SCSI technology has been around for ever and provided you go with a name brand, you shouldn't have any surprises. SCSI has been and continues to be the backbone for data storage. I have 15 year old SCSI drives that continue to spin and serve up data without ANY problems, wish I could say the same for my IDE drives.

Other Comments anyone?|||Paul, what information would be required for an analysis? I have no clue how MSSQL stores information or uses a hard drive when performing queries and inserts, etc. I just want to understand how MSSQL interacts with the hard drive... does it require more memory and not rely as heavily on the hard drive? Those types of questions.

Thanks,

Mark|||Since you are going to have high level of concurent writes to db, the logical choice is to inplement RAID10. Only few IDE hardware can support RAID10. SCSI disks are much faster and have high throughput.
I think SCSI if the only choise for production at this moment.

HTH,
OBRP

DB mirroring setup

Prepare to setup DB mirroring. Three MS 2003 servers. Two SQL 2005 standard edition as partners and one SQL 2005 Express as witness. Question:

1. Servers are under workgroup (not domain user). Is it ok to use local service account to run DB engine service on all three machine? Is SQLServerAgent service required when setup mirroring?

2. If SQL Server is running as a local service, Do I have to manually create certificates before setup mirroring?

3. After create certificates, can management studio be used to create endpoints on all three machines? If yes, how to select certificates that have been created? If no, can management studio be used to setup mirroring after endpoints have been created?

actually i'm also would like to know about the additional settings if there is. Hope can get some guidelines here. Thx

Best Regards,

Hans

DB Mirroring question

I'd like to verify that the use Asynchronous database mirroring is NOT
supported in the Standard Edition.
I've read some docs that say it isn't. However, my manager saids that
he was told it was (or would work), something about 'single stream'? I
have not been able to find any docs that talks about 'single stream'.
Can anyone advise or point me in the right direction?
thanks all,
JD
Hi Joey
"JoeyD" wrote:

> I'd like to verify that the use Asynchronous database mirroring is NOT
> supported in the Standard Edition.
> I've read some docs that say it isn't. However, my manager saids that
> he was told it was (or would work), something about 'single stream'? I
> have not been able to find any docs that talks about 'single stream'.
> Can anyone advise or point me in the right direction?
> thanks all,
> JD
>
Have you seen
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
John

DB Mirroring question

I'd like to verify that the use Asynchronous database mirroring is NOT
supported in the Standard Edition.
I've read some docs that say it isn't. However, my manager saids that
he was told it was (or would work), something about 'single stream'? I
have not been able to find any docs that talks about 'single stream'.
Can anyone advise or point me in the right direction?
thanks all,
JDHi Joey
"JoeyD" wrote:

> I'd like to verify that the use Asynchronous database mirroring is NOT
> supported in the Standard Edition.
> I've read some docs that say it isn't. However, my manager saids that
> he was told it was (or would work), something about 'single stream'? I
> have not been able to find any docs that talks about 'single stream'.
> Can anyone advise or point me in the right direction?
> thanks all,
> JD
>
Have you seen
http://www.microsoft.com/technet/pr...5/dbmirror.mspx
John

DB Mirroring question

I'd like to verify that the use Asynchronous database mirroring is NOT
supported in the Standard Edition.
I've read some docs that say it isn't. However, my manager saids that
he was told it was (or would work), something about 'single stream'? I
have not been able to find any docs that talks about 'single stream'.
Can anyone advise or point me in the right direction?
thanks all,
JDHi Joey
"JoeyD" wrote:
> I'd like to verify that the use Asynchronous database mirroring is NOT
> supported in the Standard Edition.
> I've read some docs that say it isn't. However, my manager saids that
> he was told it was (or would work), something about 'single stream'? I
> have not been able to find any docs that talks about 'single stream'.
> Can anyone advise or point me in the right direction?
> thanks all,
> JD
>
Have you seen
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
John

DB Limitation or record limitation

Hi,
Does anybody know of any DB size or record limitation in
the SQL Standard Edition DB?
I've heard that SQL may a DB limitation, I know that
Exchange Standard has a Mailbox of 16GB, and I was
wondering if there was something similiar in SQL Standard.
Thanks for any insight.See capacities and specifications in books on line. The theoretical limts
are sky high, there are other practical limits (generally budget and/or
available physical hardware)
"carl mills" <carl@.sysgbs.com> wrote in message
news:016201c34179$4692a610$a101280a@.phx.gbl...
> Hi,
> Does anybody know of any DB size or record limitation in
> the SQL Standard Edition DB?
> I've heard that SQL may a DB limitation, I know that
> Exchange Standard has a Mailbox of 16GB, and I was
> wondering if there was something similiar in SQL Standard.
> Thanks for any insight.|||Hi Chinna,
Can you send me a link to the "Maximum Capacity
Specifications" in BOL
>--Original Message--
>Hi,
>Does anybody know of any DB size or record limitation in
>the SQL Standard Edition DB?
>I've heard that SQL may a DB limitation, I know that
>Exchange Standard has a Mailbox of 16GB, and I was
>wondering if there was something similiar in SQL
Standard.
>Thanks for any insight.
>.
>|||In BOL, click on index tab... just copy and paste
"Maximum Capacity Specifications" (without double quotes).
you will get it.
Thanks
Chinna.
>--Original Message--
>Hi Chinna,
>Can you send me a link to the "Maximum Capacity
>Specifications" in BOL
>>--Original Message--
>>Hi,
>>Does anybody know of any DB size or record limitation in
>>the SQL Standard Edition DB?
>>I've heard that SQL may a DB limitation, I know that
>>Exchange Standard has a Mailbox of 16GB, and I was
>>wondering if there was something similiar in SQL
>Standard.
>>Thanks for any insight.
>>.
>.
>|||Open books online, Go / URL... Jump to this URL:
architec.chm::/8_ar_ts_8dbn.htm
If you don't have books online, see http://www.aspfaq.com/2229
You can also see http://www.aspfaq.com/2345
"Carl" <carl@.sysgbs.com> wrote in message
news:0b7b01c3417c$05199a60$a501280a@.phx.gbl...
> Hi Chinna,
> Can you send me a link to the "Maximum Capacity
> Specifications" in BOL|||http://msdn.microsoft.com/library/en-us/architec/8_ar_ts_8dbn.asp
Geoff N. Hiten
Senior Database Administrator
Careerbuilder.com
"Carl" <carl@.sysgbs.com> wrote in message
news:0b7b01c3417c$05199a60$a501280a@.phx.gbl...
> Hi Chinna,
> Can you send me a link to the "Maximum Capacity
> Specifications" in BOL
> >--Original Message--
> >Hi,
> >Does anybody know of any DB size or record limitation in
> >the SQL Standard Edition DB?
> >
> >I've heard that SQL may a DB limitation, I know that
> >Exchange Standard has a Mailbox of 16GB, and I was
> >wondering if there was something similiar in SQL
> Standard.
> >
> >Thanks for any insight.
> >.
> >