A Database without a name

Hi
By mistake I ran a SQL Script which was not completed successfully. The
script should create a database, and subsequently create tables, views etc.
The bug in the script was quite obvious, but the database was created -
without a name, and without any tables (including system tables). So - in the
server's list of databases, there is a complete empty one - again without a
name.
I cannot delete it. An attempt result in following error:
21776:[SQL-DMO] The name '' was not found in the database collection..
How can I get rid of this empty database?
Anders
How do you know there is are system tables? Have you gotten into the
database?
Can you try changing the name and then deleting it?
What version are you running?
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"Anders Balslev" <AndersBalslev@.discussions.microsoft.com> wrote in message
news:B4F5FB8B-4191-4E2D-8E19-F1FF84ABD636@.microsoft.com...
> Hi
> By mistake I ran a SQL Script which was not completed successfully. The
> script should create a database, and subsequently create tables, views
> etc.
> The bug in the script was quite obvious, but the database was created -
> without a name, and without any tables (including system tables). So - in
> the
> server's list of databases, there is a complete empty one - again without
> a
> name.
> I cannot delete it. An attempt result in following error:
> 21776:[SQL-DMO] The name '' was not found in the database collection..
> How can I get rid of this empty database?
> Anders
|||Just to add to what Tibor said, you can create a database whose name appears
to be empty but not. For instance, you can run the following statement:
create database [ ] -- with a blank inside the brackets
I'd try the following to see what physical files the database is using:
select name, filename from master..sysaltfiles
Linchi
"Anders Balslev" wrote:

> Hi
> By mistake I ran a SQL Script which was not completed successfully. The
> script should create a database, and subsequently create tables, views etc.
> The bug in the script was quite obvious, but the database was created -
> without a name, and without any tables (including system tables). So - in the
> server's list of databases, there is a complete empty one - again without a
> name.
> I cannot delete it. An attempt result in following error:
> 21776:[SQL-DMO] The name '' was not found in the database collection..
> How can I get rid of this empty database?
> Anders
|||Hi Tibor
I did as you told, and one of the rows affected was
**
(no space between the asterix)
b.t.w. I didnt tell that it was SQL Server 2000
I presume that I can't just delete it manually from the
master.dbo.sysdatabases
Anders
"Tibor Karaszi" wrote:

> I suggest you first determine whether the database is truly without name or if the name is a blank
> (space) character or similar. Please remember to post version of SQL Server. I assume 2000 (due to
> the DMO error). Here's what I would start with:
> SELECT '*' + name + '*' FROM master.dbo.sysdatabases
> See if you find your database and whether there is anything inside the asterisks.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Anders Balslev" <AndersBalslev@.discussions.microsoft.com> wrote in message
> news:B4F5FB8B-4191-4E2D-8E19-F1FF84ABD636@.microsoft.com...
>
|||Take a look here:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=351489&SiteID=1
...I was going to suggest "DROP DATABASE []", but it looks like there are a
few options on this page, one of which was reported to have worked.
"Anders Balslev" <AndersBalslev@.discussions.microsoft.com> wrote in message
news:B4F5FB8B-4191-4E2D-8E19-F1FF84ABD636@.microsoft.com...
> Hi
> By mistake I ran a SQL Script which was not completed successfully. The
> script should create a database, and subsequently create tables, views
> etc.
> The bug in the script was quite obvious, but the database was created -
> without a name, and without any tables (including system tables). So - in
> the
> server's list of databases, there is a complete empty one - again without
> a
> name.
> I cannot delete it. An attempt result in following error:
> 21776:[SQL-DMO] The name '' was not found in the database collection..
> How can I get rid of this empty database?
> Anders
|||No, you can't delete it manually because that won't get rid of all the
associated information, but what you can do in SQL 2000 (but not in 2005) is
to manually update the system table sysdatabases to give it a name, and then
you should be able to get rid of it.
Did you try changing the name as I suggested from the EM tool? What
happened?
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"Anders Balslev" <AndersBalslev@.discussions.microsoft.com> wrote in message
news:C9214C27-9448-41EB-9C39-3ED346EFDDF8@.microsoft.com...[vbcol=seagreen]
> Hi Tibor
> I did as you told, and one of the rows affected was
> **
> (no space between the asterix)
> b.t.w. I didnt tell that it was SQL Server 2000
> I presume that I can't just delete it manually from the
> master.dbo.sysdatabases
> Anders
> "Tibor Karaszi" wrote:

A Database without a name

Hi
By mistake I ran a SQL Script which was not completed successfully. The
script should create a database, and subsequently create tables, views etc.
The bug in the script was quite obvious, but the database was created -
without a name, and without any tables (including system tables). So - in the
server's list of databases, there is a complete empty one - again without a
name.
I cannot delete it. An attempt result in following error:
21776:[SQL-DMO] The name '' was not found in the database collection..
How can I get rid of this empty database?
AndersHow do you know there is are system tables? Have you gotten into the
database?
Can you try changing the name and then deleting it?
What version are you running?
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"Anders Balslev" <AndersBalslev@.discussions.microsoft.com> wrote in message
news:B4F5FB8B-4191-4E2D-8E19-F1FF84ABD636@.microsoft.com...
> Hi
> By mistake I ran a SQL Script which was not completed successfully. The
> script should create a database, and subsequently create tables, views
> etc.
> The bug in the script was quite obvious, but the database was created -
> without a name, and without any tables (including system tables). So - in
> the
> server's list of databases, there is a complete empty one - again without
> a
> name.
> I cannot delete it. An attempt result in following error:
> 21776:[SQL-DMO] The name '' was not found in the database collection..
> How can I get rid of this empty database?
> Anders|||I suggest you first determine whether the database is truly without name or if the name is a blank
(space) character or similar. Please remember to post version of SQL Server. I assume 2000 (due to
the DMO error). Here's what I would start with:
SELECT '*' + name + '*' FROM master.dbo.sysdatabases
See if you find your database and whether there is anything inside the asterisks.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Anders Balslev" <AndersBalslev@.discussions.microsoft.com> wrote in message
news:B4F5FB8B-4191-4E2D-8E19-F1FF84ABD636@.microsoft.com...
> Hi
> By mistake I ran a SQL Script which was not completed successfully. The
> script should create a database, and subsequently create tables, views etc.
> The bug in the script was quite obvious, but the database was created -
> without a name, and without any tables (including system tables). So - in the
> server's list of databases, there is a complete empty one - again without a
> name.
> I cannot delete it. An attempt result in following error:
> 21776:[SQL-DMO] The name '' was not found in the database collection..
> How can I get rid of this empty database?
> Anders|||Just to add to what Tibor said, you can create a database whose name appears
to be empty but not. For instance, you can run the following statement:
create database [ ] -- with a blank inside the brackets
I'd try the following to see what physical files the database is using:
select name, filename from master..sysaltfiles
Linchi
"Anders Balslev" wrote:
> Hi
> By mistake I ran a SQL Script which was not completed successfully. The
> script should create a database, and subsequently create tables, views etc.
> The bug in the script was quite obvious, but the database was created -
> without a name, and without any tables (including system tables). So - in the
> server's list of databases, there is a complete empty one - again without a
> name.
> I cannot delete it. An attempt result in following error:
> 21776:[SQL-DMO] The name '' was not found in the database collection..
> How can I get rid of this empty database?
> Anders|||Hi Tibor
I did as you told, and one of the rows affected was
**
(no space between the asterix)
b.t.w. I didnt tell that it was SQL Server 2000
I presume that I can't just delete it manually from the
master.dbo.sysdatabases
Anders
"Tibor Karaszi" wrote:
> I suggest you first determine whether the database is truly without name or if the name is a blank
> (space) character or similar. Please remember to post version of SQL Server. I assume 2000 (due to
> the DMO error). Here's what I would start with:
> SELECT '*' + name + '*' FROM master.dbo.sysdatabases
> See if you find your database and whether there is anything inside the asterisks.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Anders Balslev" <AndersBalslev@.discussions.microsoft.com> wrote in message
> news:B4F5FB8B-4191-4E2D-8E19-F1FF84ABD636@.microsoft.com...
> > Hi
> >
> > By mistake I ran a SQL Script which was not completed successfully. The
> > script should create a database, and subsequently create tables, views etc.
> > The bug in the script was quite obvious, but the database was created -
> > without a name, and without any tables (including system tables). So - in the
> > server's list of databases, there is a complete empty one - again without a
> > name.
> > I cannot delete it. An attempt result in following error:
> > 21776:[SQL-DMO] The name '' was not found in the database collection..
> > How can I get rid of this empty database?
> > Anders
>|||Take a look here:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=351489&SiteID=1
...I was going to suggest "DROP DATABASE []", but it looks like there are a
few options on this page, one of which was reported to have worked. :)
"Anders Balslev" <AndersBalslev@.discussions.microsoft.com> wrote in message
news:B4F5FB8B-4191-4E2D-8E19-F1FF84ABD636@.microsoft.com...
> Hi
> By mistake I ran a SQL Script which was not completed successfully. The
> script should create a database, and subsequently create tables, views
> etc.
> The bug in the script was quite obvious, but the database was created -
> without a name, and without any tables (including system tables). So - in
> the
> server's list of databases, there is a complete empty one - again without
> a
> name.
> I cannot delete it. An attempt result in following error:
> 21776:[SQL-DMO] The name '' was not found in the database collection..
> How can I get rid of this empty database?
> Anders|||No, you can't delete it manually because that won't get rid of all the
associated information, but what you can do in SQL 2000 (but not in 2005) is
to manually update the system table sysdatabases to give it a name, and then
you should be able to get rid of it.
Did you try changing the name as I suggested from the EM tool? What
happened?
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"Anders Balslev" <AndersBalslev@.discussions.microsoft.com> wrote in message
news:C9214C27-9448-41EB-9C39-3ED346EFDDF8@.microsoft.com...
> Hi Tibor
> I did as you told, and one of the rows affected was
> **
> (no space between the asterix)
> b.t.w. I didnt tell that it was SQL Server 2000
> I presume that I can't just delete it manually from the
> master.dbo.sysdatabases
> Anders
> "Tibor Karaszi" wrote:
>> I suggest you first determine whether the database is truly without name
>> or if the name is a blank
>> (space) character or similar. Please remember to post version of SQL
>> Server. I assume 2000 (due to
>> the DMO error). Here's what I would start with:
>> SELECT '*' + name + '*' FROM master.dbo.sysdatabases
>> See if you find your database and whether there is anything inside the
>> asterisks.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Anders Balslev" <AndersBalslev@.discussions.microsoft.com> wrote in
>> message
>> news:B4F5FB8B-4191-4E2D-8E19-F1FF84ABD636@.microsoft.com...
>> > Hi
>> >
>> > By mistake I ran a SQL Script which was not completed successfully. The
>> > script should create a database, and subsequently create tables, views
>> > etc.
>> > The bug in the script was quite obvious, but the database was created -
>> > without a name, and without any tables (including system tables). So -
>> > in the
>> > server's list of databases, there is a complete empty one - again
>> > without a
>> > name.
>> > I cannot delete it. An attempt result in following error:
>> > 21776:[SQL-DMO] The name '' was not found in the database collection..
>> > How can I get rid of this empty database?
>> > Anders
>>

A data source instance has not been supplied for the data source

Hi Guys,

I have create a report and it works in development mode. But when I call this report from aspx page it give me above error message. Please let me know how can I setup datasource of this report at runtime. Below is my code

Regards

ReportParameter[] rptPara = new ReportParameter[1];

rptPara[0] = new ReportParameter("rDate", WebDateChooser1.Text, false);

ReportViewer1.LocalReport.ReportPath = @."C:Business\RPT585.rdl";

ReportViewer1.LocalReport.SetParameters(rptPara);

ReportViewer1.LocalReport.Refresh();

Please anybody could let me guide here....

|||

This is how you can provide DataSource information to report at runtime.

Example:

ObjectDataSource objAdventureWorks = new ObjectDataSource("MyData", "GetDataAddress");

objAdventureWorks.ID = "Adventureworks";

this.Controls.Add(objAdventureWorks);

this.ReportViewer.LocalReport.DataSources.Add(new ReportDataSource("AdventureWorks2000", "Adventureworks"));

|||

I have added the datasource of my report but still keep getting this error message. Please let me guide how to fix this error. adn how to set data source instance. Below is my code

ReportParameter[] rptPara = new ReportParameter[1];

rptPara[0] = new ReportParameter("rDate", WebDateChooser1.Text, false);

ReportViewer1.LocalReport.ReportPath = @."C:\business\RPT528.rdl";

ReportViewer1.LocalReport.SetParameters(rptPara);

ReportViewer1.LocalReport.DataSources.Add(new ReportDataSource("dsCustomers"));

ReportViewer1.LocalReport.Refresh();

|||

http://blogs.msdn.com/bimusings/archive/2005/07/01/434659.aspx

I think this article should answer your question. I was experiencing the same error and Russell's work-around fixed it.

TF

A Custom component for use as a VIEW in SSIS- Is it possible to create one MERGE like component

Hi all

I'm into a project which uses a lot of views for joining 2 or more tables. Using the MERGE component in SSIS will be a huge effort coz it only has 2 inputs and I gotta SORT the input too.

Isnt it possible to have a VIEW like component that joins more than 2 tables and DOESNT need sorting?

(I've thought about creating views in database engine but it breaks my data floe in SSIS and is'nt a practical solution)

You have a few options. You can implement views in the database engine (not sure why it breaks your data flow, but it's perhaps the best option), you can join your tables via SQL in an OLE DB Source component, or you can use multiple OLE DB Source connections and then use one or more merge join transformations.

Just an FYI - If your data is sorted with an ORDER BY clause in the SQL statement, you can set the ISSORTED flag to true (1) on the OLE DB source and a SORT component won't be required.|||

Thanks Phil for the quick response..

I said "using Views breaks my data flow" - I meant all views cannot be represented in SSIS data flow right? so it becomes difficult later on to understand/change the data flow coz I'll have to check views in database manager and other stuff in SSIS. OR is there a way we can export the whole data flow into some kinda diagram so I can see it all at once? (I don't think there is right?)

So my problem boils down to creating a VIEW type custom component. I have seen other custom component samples but don't know how to do JOINs via code. Can you give me a brief idea for, say, if I have to join 2 tables how many PipelineBuffers I'll need (2 for input and 1 for output?) and how do I match values between the two joining columns(col1.value==col2.value?)?

Guess this is a big question but Im sure it'll help a lot of developers.

thanks

Ravi

|||

If you want to power and performance gain of views and T-SQL, then use T-SQL. Use the relational engine for what it is good for is my opinion. A component to avoid having a view/SELECT when it would do the job best of all is just daft.

If you want some of the re-use of a view but without the object itself, you may want to look at Data Source Views. They are a design-time only feature, but are stored in your SSIS project so may meet your requirement. So you would use the same SELECT statement as in the view, but it would not be a SQL object.

|||

Hi Darren, I think u didnt get my problem right?

I just want help creating a MERGE type component which can join more than 2 inputs. I understand I can use more than one MERGEs to do the same, which ill do if creating the component is a pain ..

A Custom component for use as a VIEW in SSIS- Is it possible to create one MERGE like component

Hi all

I'm into a project which uses a lot of views for joining 2 or more tables. Using the MERGE component in SSIS will be a huge effort coz it only has 2 inputs and I gotta SORT the input too.

Isnt it possible to have a VIEW like component that joins more than 2 tables and DOESNT need sorting?

(I've thought about creating views in database engine but it breaks my data floe in SSIS and is'nt a practical solution)

You have a few options. You can implement views in the database engine (not sure why it breaks your data flow, but it's perhaps the best option), you can join your tables via SQL in an OLE DB Source component, or you can use multiple OLE DB Source connections and then use one or more merge join transformations.

Just an FYI - If your data is sorted with an ORDER BY clause in the SQL statement, you can set the ISSORTED flag to true (1) on the OLE DB source and a SORT component won't be required.|||

Thanks Phil for the quick response..

I said "using Views breaks my data flow" - I meant all views cannot be represented in SSIS data flow right? so it becomes difficult later on to understand/change the data flow coz I'll have to check views in database manager and other stuff in SSIS. OR is there a way we can export the whole data flow into some kinda diagram so I can see it all at once? (I don't think there is right?)

So my problem boils down to creating a VIEW type custom component. I have seen other custom component samples but don't know how to do JOINs via code. Can you give me a brief idea for, say, if I have to join 2 tables how many PipelineBuffers I'll need (2 for input and 1 for output?) and how do I match values between the two joining columns(col1.value==col2.value?)?

Guess this is a big question but Im sure it'll help a lot of developers.

thanks

Ravi

|||

If you want to power and performance gain of views and T-SQL, then use T-SQL. Use the relational engine for what it is good for is my opinion. A component to avoid having a view/SELECT when it would do the job best of all is just daft.

If you want some of the re-use of a view but without the object itself, you may want to look at Data Source Views. They are a design-time only feature, but are stored in your SSIS project so may meet your requirement. So you would use the same SELECT statement as in the view, but it would not be a SQL object.

|||

Hi Darren, I think u didnt get my problem right?

I just want help creating a MERGE type component which can join more than 2 inputs. I understand I can use more than one MERGEs to do the same, which ill do if creating the component is a pain ..

sql

A Custom component for use as a VIEW in SSIS- Is it possible to create one MERGE like component

Hi all

I'm into a project which uses a lot of views for joining 2 or more tables. Using the MERGE component in SSIS will be a huge effort coz it only has 2 inputs and I gotta SORT the input too.

Isnt it possible to have a VIEW like component that joins more than 2 tables and DOESNT need sorting?

(I've thought about creating views in database engine but it breaks my data floe in SSIS and is'nt a practical solution)

You have a few options. You can implement views in the database engine (not sure why it breaks your data flow, but it's perhaps the best option), you can join your tables via SQL in an OLE DB Source component, or you can use multiple OLE DB Source connections and then use one or more merge join transformations.

Just an FYI - If your data is sorted with an ORDER BY clause in the SQL statement, you can set the ISSORTED flag to true (1) on the OLE DB source and a SORT component won't be required.|||

Thanks Phil for the quick response..

I said "using Views breaks my data flow" - I meant all views cannot be represented in SSIS data flow right? so it becomes difficult later on to understand/change the data flow coz I'll have to check views in database manager and other stuff in SSIS. OR is there a way we can export the whole data flow into some kinda diagram so I can see it all at once? (I don't think there is right?)

So my problem boils down to creating a VIEW type custom component. I have seen other custom component samples but don't know how to do JOINs via code. Can you give me a brief idea for, say, if I have to join 2 tables how many PipelineBuffers I'll need (2 for input and 1 for output?) and how do I match values between the two joining columns(col1.value==col2.value?)?

Guess this is a big question but Im sure it'll help a lot of developers.

thanks

Ravi

|||

If you want to power and performance gain of views and T-SQL, then use T-SQL. Use the relational engine for what it is good for is my opinion. A component to avoid having a view/SELECT when it would do the job best of all is just daft.

If you want some of the re-use of a view but without the object itself, you may want to look at Data Source Views. They are a design-time only feature, but are stored in your SSIS project so may meet your requirement. So you would use the same SELECT statement as in the view, but it would not be a SQL object.

|||

Hi Darren, I think u didnt get my problem right?

I just want help creating a MERGE type component which can join more than 2 inputs. I understand I can use more than one MERGEs to do the same, which ill do if creating the component is a pain ..

A conceptual question about RS (when is it usefull)

In my department we are trying to benefit from the RS: we create a lot of
reports for the Marketing, and generally supply them through an Excel
spresdsheet:
1. Ad hoc reports with data which won't be updated.
2. Reports connected to views which are updated once they are oppened by the
user (=the Excel spredsheet is oppened).
3. Reports connected to tables which are daily updated (if the view is to
heavy).
In all the three situations, the RS doesn't help us.
I guess this tool is usefull for information departments who want to publish
reports to many subacribers at once
or to subscribers who need a "hard copy" of the report (=to print it)
or for interactive reports in which the user has to choose values (a year or
a customer or a product) and we don't want to write code.
Am I right?
Any comment or suggestion will be wellcome!RS is not excel and Excel is no RS. You have gotten used to Excel for
reporting and that is fine but it seems to me that you are approaching this
specifically from the viewpoint of a spreadsheet. If you look at what RS can
do you will find that you will be designing reports in a whole new way.
You say that RS doesn't help you. If you are already really skilled in Excel
and want to keep doing things the way you are then fine. It seems to me you
have already made your decision.
Some capabilities of RS:
1. You can schedule long running reports to run at a certain time, then the
user will use that snapshot.
2. Lots of caching configurations you can do
3. Drill through. This is huge. Instead of one mega report, put the data
they need and then provide links that pull up additional information in
reports passing the parameters to the report.
I'm not sure why you say RS doesn't help you in the three items you list.
Seems like it does for #3 for sure. Perhaps #2 as well.
As far as interactive reports, you can set defaults so the user doesn't have
to make a decision but can change it if they want to.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Geri Reshef" <GeriR@.Dubek.co.il> wrote in message
news:%23NwTAWI%23EHA.3260@.TK2MSFTNGP14.phx.gbl...
> In my department we are trying to benefit from the RS: we create a lot of
> reports for the Marketing, and generally supply them through an Excel
> spresdsheet:
> 1. Ad hoc reports with data which won't be updated.
> 2. Reports connected to views which are updated once they are oppened by
the
> user (=the Excel spredsheet is oppened).
> 3. Reports connected to tables which are daily updated (if the view is to
> heavy).
> In all the three situations, the RS doesn't help us.
> I guess this tool is usefull for information departments who want to
publish
> reports to many subacribers at once
> or to subscribers who need a "hard copy" of the report (=to print it)
> or for interactive reports in which the user has to choose values (a year
or
> a customer or a product) and we don't want to write code.
> Am I right?
> Any comment or suggestion will be wellcome!
>

A Chart for Each Client

I'm trying to create a chart for each client.
In a DataSet, they are returned in a sorted order like this:
ClientName Month Sales
-- -- --
Client 1 1 500
Client 1 2 100
...
Client 1 10 900
Client 2 1 100
Client 2 2 200
...
Client 2 10 800
I'd like to have two charts, Client 1 and Client 2 showing their own
trend.
However, so far I get only ONE chart, either a sum, or the first client
group if it's not sum.
I don't think it will take one query per client.
Thanks.I think I got it by browsing some QA here, simply by putting it in a
group's header or footer in a table.|||Yes, that is correct. If you place a chart in a table detail section, every
chart will just get one detail data row (i.e. essentially just one
datapoint) and this is not what you want. Placing the chart however in the
group's header or footer will generate a chart from all the detail rows that
are contained in the current group.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
<hifchan@.yahoo.com> wrote in message
news:1108483860.264648.286130@.c13g2000cwb.googlegroups.com...
>I think I got it by browsing some QA here, simply by putting it in a
> group's header or footer in a table.
>sql

8198 error

sql2k sp3
win2k sp4
Im trying to create a Pull Subscription for replication and get "Error 8198:
Could not obtain information about Windows NT group/ user 'domain/ user'".
I read this:
http://support.microsoft.com/?kbid=834124
But both boxes are in the same domain and the same subnet. Both use the same
domain admin account for SQL Server and the Agent accounts.
I also read this:
http://support.microsoft.com/?kbid=838460
But Im not about to install sp4 Beta on anything. SA is the owner of all the
jobs.
Is there anything else I can do?
TIA, ChrisR
we are receiving these all over the place where I work. They are normally
solved by changing the job owner to sa and restarting the job. It seems that
a recent update has caused this problem/behavior.
"ChrisR" <noemail@.bla.com> wrote in message
news:%237FEr0PTFHA.3696@.TK2MSFTNGP15.phx.gbl...
> sql2k sp3
> win2k sp4
> Im trying to create a Pull Subscription for replication and get "Error
> 8198:
> Could not obtain information about Windows NT group/ user 'domain/ user'".
> I read this:
> http://support.microsoft.com/?kbid=834124
> But both boxes are in the same domain and the same subnet. Both use the
> same
> domain admin account for SQL Server and the Agent accounts.
> I also read this:
> http://support.microsoft.com/?kbid=838460
> But Im not about to install sp4 Beta on anything. SA is the owner of all
> the jobs.
> Is there anything else I can do?
> TIA, ChrisR
>
|||It would have been easier if that had been it. I didnt realize that these
two boxes are in they're own little world, and that connections to them can
be rather difficult.
Thanks Hillary.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23B19ZdQTFHA.3464@.tk2msftngp13.phx.gbl...
> we are receiving these all over the place where I work. They are normally
> solved by changing the job owner to sa and restarting the job. It seems
> that a recent update has caused this problem/behavior.
> "ChrisR" <noemail@.bla.com> wrote in message
> news:%237FEr0PTFHA.3696@.TK2MSFTNGP15.phx.gbl...
>

64bit vs 32bit

If I create a database on 64bit version of SQL 2005 and then copy it to a
32bit version SQL 2005 will that database still work? and/or will
adminstrators have to make setting changes?All Editions of SQL within a major version maintain user database on-disk
compatibility across all architectures. That is a very complex way of
saying that any database created on any version/edition/processor
combination of SQL 2005 can be restored or copied to a SQL instance on any
other version/edition/processor combination. The sole exception is that SQL
Express will not accept a database over its 4GB size limit.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Sean" <Sean@.discussions.microsoft.com> wrote in message
news:C85E4CF8-BA5D-4300-898F-49650A72627C@.microsoft.com...
> If I create a database on 64bit version of SQL 2005 and then copy it to a
> 32bit version SQL 2005 will that database still work? and/or will
> adminstrators have to make setting changes?|||In other words "yes it will work, all other things being equal".
;)
*mike hodgson*
http://sqlnerd.blogspot.com
Geoff N. Hiten wrote:

>All Editions of SQL within a major version maintain user database on-disk
>compatibility across all architectures. That is a very complex way of
>saying that any database created on any version/edition/processor
>combination of SQL 2005 can be restored or copied to a SQL instance on any
>other version/edition/processor combination. The sole exception is that SQ
L
>Express will not accept a database over its 4GB size limit.
>
>

64bit vs 32bit

If I create a database on 64bit version of SQL 2005 and then copy it to a
32bit version SQL 2005 will that database still work? and/or will
adminstrators have to make setting changes?All Editions of SQL within a major version maintain user database on-disk
compatibility across all architectures. That is a very complex way of
saying that any database created on any version/edition/processor
combination of SQL 2005 can be restored or copied to a SQL instance on any
other version/edition/processor combination. The sole exception is that SQL
Express will not accept a database over its 4GB size limit.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Sean" <Sean@.discussions.microsoft.com> wrote in message
news:C85E4CF8-BA5D-4300-898F-49650A72627C@.microsoft.com...
> If I create a database on 64bit version of SQL 2005 and then copy it to a
> 32bit version SQL 2005 will that database still work? and/or will
> adminstrators have to make setting changes?|||This is a multi-part message in MIME format.
--080803020901070905080703
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
In other words "yes it will work, all other things being equal".
;)
--
*mike hodgson*
http://sqlnerd.blogspot.com
Geoff N. Hiten wrote:
>All Editions of SQL within a major version maintain user database on-disk
>compatibility across all architectures. That is a very complex way of
>saying that any database created on any version/edition/processor
>combination of SQL 2005 can be restored or copied to a SQL instance on any
>other version/edition/processor combination. The sole exception is that SQL
>Express will not accept a database over its 4GB size limit.
>
>
--080803020901070905080703
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>In other words "yes it will work, all other things being equal".<br>
<br>
;)<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Geoff N. Hiten wrote:
<blockquote cite="midOflGC5GoGHA.4172@.TK2MSFTNGP03.phx.gbl" type="cite">
<pre wrap="">All Editions of SQL within a major version maintain user database on-disk
compatibility across all architectures. That is a very complex way of
saying that any database created on any version/edition/processor
combination of SQL 2005 can be restored or copied to a SQL instance on any
other version/edition/processor combination. The sole exception is that SQL
Express will not accept a database over its 4GB size limit.
</pre>
</blockquote>
</body>
</html>
--080803020901070905080703--

64 bit windows 2003 sp2 SQL SERVER 2005 Linked server

The server is IBM XS 466.
The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
(64bit),I want to create a linked server for Oracle,I have installed ORACLE
Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
2005,i can't find 'MSDAORA',it caust i can't create linked server for
oracle.msbut I can find some drivers about oracle in ODBC,but must run
'c:\windows\system32\odbcad32.exe'
This proble puzzle me for some days
Standing on Shoulders of Giants
* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
My first guess is that the 64 version of SQL Server can only load 64-bit
drivers. This means the old OleDb driver and ODBC driver are not
compatible.
Either reinstall SQL server as 32-bit binaries or find a 64-bit
compatible driver for Oracle.
Jesse
|||* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
You can find the 64-bit OleDB Driver here:
http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
That should get things in working order.
Jesse
|||I haved installed 64bit Driver for Oracle,but the proble is the same,it has
other approach?
Standing on Shoulders of Giants
"Jesse Houwing" wrote:

> * fds2003 wrote, On 4-7-2007 12:32:
> You can find the 64-bit OleDB Driver here:
> http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
> That should get things in working order.
> Jesse
>

64 bit windows 2003 sp2 SQL SERVER 2005 Linked server

The server is IBM XS 466.
The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
(64bit),I want to create a linked server for Oracle,I have installed ORACLE
Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
2005,i can't find 'MSDAORA',it caust i can't create linked server for
oracle.msbut I can find some drivers about oracle in ODBC,but must run
'c:\windows\system32\odbcad32.exe'
This proble puzzle me for some days
--
Standing on Shoulders of Giants* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACL
E
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
My first guess is that the 64 version of SQL Server can only load 64-bit
drivers. This means the old OleDb driver and ODBC driver are not
compatible.
Either reinstall SQL server as 32-bit binaries or find a 64-bit
compatible driver for Oracle.
Jesse|||* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACL
E
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
You can find the 64-bit OleDB Driver here:
[url]http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html[/u
rl]
That should get things in working order.
Jesse|||I haved installed 64bit Driver for Oracle,but the proble is the same,it has
other approach?
--
Standing on Shoulders of Giants
"Jesse Houwing" wrote:

> * fds2003 wrote, On 4-7-2007 12:32:
> You can find the 64-bit OleDB Driver here:
> [url]http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html[
/url]
> That should get things in working order.
> Jesse
>

64 bit windows 2003 sp2 SQL SERVER 2005 Linked server

The server is IBM XS 466.
The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
(64bit),I want to create a linked server for Oracle,I have installed ORACLE
Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
2005,i can't find 'MSDAORA',it caust i can't create linked server for
oracle.msbut I can find some drivers about oracle in ODBC,but must run
'c:\windows\system32\odbcad32.exe'
This proble puzzle me for some days
--
Standing on Shoulders of Giants* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
My first guess is that the 64 version of SQL Server can only load 64-bit
drivers. This means the old OleDb driver and ODBC driver are not
compatible.
Either reinstall SQL server as 32-bit binaries or find a 64-bit
compatible driver for Oracle.
Jesse|||* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
You can find the 64-bit OleDB Driver here:
http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
That should get things in working order.
Jesse|||I haved installed 64bit Driver for Oracle,but the proble is the same,it has
other approach?
--
Standing on Shoulders of Giants
"Jesse Houwing" wrote:
> * fds2003 wrote, On 4-7-2007 12:32:
> > The server is IBM XS 466.
> > The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> > (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> > Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> > 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> > oracle.msbut I can find some drivers about oracle in ODBC,but must run
> > 'c:\windows\system32\odbcad32.exe'
> > This proble puzzle me for some days
> You can find the 64-bit OleDB Driver here:
> http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
> That should get things in working order.
> Jesse
>

64 bit Server Aliases SQL 2005

Does anyone know how to create SQL Server aliases for Itanium servers?

Alternatively does anyone know how to use SMO to create a SQLAliasCollection for a specific server? I can't seem to find how to get that collection.

I've added aliases that work for 32 bit applications but they don't seem to be used for 64 bit applications.

Please check my blog for alias. http://blogs.msdn.com/sql_protocols/archive/2007/01/07/connection-alias.aspx

You need to use 64-bit cliconfg.exe or SQL Server Connection Manager to create the alias.

|||

Thanks. It turns out alias are working fine for 64 bit and we need to add the 32 bit. The problem turned out to be that I can't connect from an Itanium Back to the itanium using a different name. When we do, NT credentials are getting blocked. We can connect to other machines using aliases, just not back to the same machine. We're investigating how to get around that at the moment :)

6.5 to 6.5

I want to upgrade our 6.5 sql server to sql server 2000 but first I
want to create another 6.5 first. This way when I screw the pooch I
won't take down our only database.
Anyway I was planning on creating a new database and then restore it
with a dump from the original. If there is an easier way please let
me know.
I've been making daily backups via a CD burner of the folder MSSQL and
backing it up once a week with a dat drive. I"ve also started doing
the dumps each day also.
As you can probably tell I've very new to this.
We use the Platypus 3.0 database frontend by Boardtown.
Thanks for all the help you can give me.<kg7poe@.sti.net> wrote in message
news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.4ax.com...
> I want to upgrade our 6.5 sql server to sql server 2000 but first I
> want to create another 6.5 first. This way when I screw the pooch I
> won't take down our only database.
> Anyway I was planning on creating a new database and then restore it
> with a dump from the original. If there is an easier way please let
> me know.
Not sure whether dumps from 6.5 can be read but to me, it sounds better to
have 2 boxes (or one box with two SQL instances). One with SQl 2000 and one
with 6.5. Run the import database tool, which will copy all objects and data
to SQL 2000.|||Hi,
(You cant restore a SQL 6.5 server database to SQL 2000 server due to
architectural changes.)
The only way to upgrade SQL 6.5 database to SQL 2000 is using the "Upgrade
Wizard" coming with SQL 2000.
You can either perform the upgrade :-
1. In the network using Named pipes protocol
2. Install SQL 6.5 in new server and have the upgrade in the same server
Steps for 1.
1. Install SQL 2000 and SP3a
2. Install SQL 6.5 sp5a
3. In the SQL 2000 server use the upgrade wizard to upgrade. This wizard
will point to a step by upgrade.
Steps for 2.
1. Install SQL 2000 and SP3a in New server
2. Install SQL 6.5 and SP5a ina new server (With the same folder structure
as existing server)
3. Stop SQL 6.5 server in both servers
4. Copy the physical DAT files (Data and log files) from Existing to new
server in the same folder including system databases
5. STArt SQL 6.5 in server, this will make the new SQL 6.5 server same as
existing
7. In the SQL 2000 server use the upgrade wizard to upgrade. This wizard
will point to a step by upgrade.
Second step will be fast since the upgrade is happening in the same machine.
Incase if you are using the First step then ensure that network is up and
stable.
Thanks
Hari
MCDBA
<kg7poe@.sti.net> wrote in message
news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.4ax.com...
> I want to upgrade our 6.5 sql server to sql server 2000 but first I
> want to create another 6.5 first. This way when I screw the pooch I
> won't take down our only database.
> Anyway I was planning on creating a new database and then restore it
> with a dump from the original. If there is an easier way please let
> me know.
>
> I've been making daily backups via a CD burner of the folder MSSQL and
> backing it up once a week with a dat drive. I"ve also started doing
> the dumps each day also.
> As you can probably tell I've very new to this.
> We use the Platypus 3.0 database frontend by Boardtown.
>
> Thanks for all the help you can give me.|||On Sun, 16 May 2004 23:05:51 +0200, "Egbert Nierop \(MVP for IIS\)"
<egbert_nierop@.nospam.invalid> wrote:
><kg7poe@.sti.net> wrote in message
>news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.4ax.com...
>> I want to upgrade our 6.5 sql server to sql server 2000 but first I
>> want to create another 6.5 first. This way when I screw the pooch I
>> won't take down our only database.
>> Anyway I was planning on creating a new database and then restore it
>> with a dump from the original. If there is an easier way please let
>> me know.
>Not sure whether dumps from 6.5 can be read but to me, it sounds better to
>have 2 boxes (or one box with two SQL instances). One with SQl 2000 and one
>with 6.5. Run the import database tool, which will copy all objects and data
>to SQL 2000.
>
Actually I want to resotre another 6.5 with a dump from the original.
Of course I can't even get the new one to work with the backup
database. I made sure its on the same hard drive letter and even
copied over the whole MSSQL folder but so far no luck.

6.5 to 6.5

I want to upgrade our 6.5 sql server to sql server 2000 but first I
want to create another 6.5 first. This way when I screw the pooch I
won't take down our only database.
Anyway I was planning on creating a new database and then restore it
with a dump from the original. If there is an easier way please let
me know.
I've been making daily backups via a CD burner of the folder MSSQL and
backing it up once a week with a dat drive. I"ve also started doing
the dumps each day also.
As you can probably tell I've very new to this.
We use the Platypus 3.0 database frontend by Boardtown.
Thanks for all the help you can give me.
<kg7poe@.sti.net> wrote in message
news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.4ax.com...
> I want to upgrade our 6.5 sql server to sql server 2000 but first I
> want to create another 6.5 first. This way when I screw the pooch I
> won't take down our only database.
> Anyway I was planning on creating a new database and then restore it
> with a dump from the original. If there is an easier way please let
> me know.
Not sure whether dumps from 6.5 can be read but to me, it sounds better to
have 2 boxes (or one box with two SQL instances). One with SQl 2000 and one
with 6.5. Run the import database tool, which will copy all objects and data
to SQL 2000.
|||Hi,
(You cant restore a SQL 6.5 server database to SQL 2000 server due to
architectural changes.)
The only way to upgrade SQL 6.5 database to SQL 2000 is using the "Upgrade
Wizard" coming with SQL 2000.
You can either perform the upgrade :-
1. In the network using Named pipes protocol
2. Install SQL 6.5 in new server and have the upgrade in the same server
Steps for 1.
1. Install SQL 2000 and SP3a
2. Install SQL 6.5 sp5a
3. In the SQL 2000 server use the upgrade wizard to upgrade. This wizard
will point to a step by upgrade.
Steps for 2.
1. Install SQL 2000 and SP3a in New server
2. Install SQL 6.5 and SP5a ina new server (With the same folder structure
as existing server)
3. Stop SQL 6.5 server in both servers
4. Copy the physical DAT files (Data and log files) from Existing to new
server in the same folder including system databases
5. STArt SQL 6.5 in server, this will make the new SQL 6.5 server same as
existing
7. In the SQL 2000 server use the upgrade wizard to upgrade. This wizard
will point to a step by upgrade.
Second step will be fast since the upgrade is happening in the same machine.
Incase if you are using the First step then ensure that network is up and
stable.
Thanks
Hari
MCDBA
<kg7poe@.sti.net> wrote in message
news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.4ax.com...
> I want to upgrade our 6.5 sql server to sql server 2000 but first I
> want to create another 6.5 first. This way when I screw the pooch I
> won't take down our only database.
> Anyway I was planning on creating a new database and then restore it
> with a dump from the original. If there is an easier way please let
> me know.
>
> I've been making daily backups via a CD burner of the folder MSSQL and
> backing it up once a week with a dat drive. I"ve also started doing
> the dumps each day also.
> As you can probably tell I've very new to this.
> We use the Platypus 3.0 database frontend by Boardtown.
>
> Thanks for all the help you can give me.
|||On Sun, 16 May 2004 23:05:51 +0200, "Egbert Nierop \(MVP for IIS\)"
<egbert_nierop@.nospam.invalid> wrote:

><kg7poe@.sti.net> wrote in message
>news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.4ax.com.. .
>Not sure whether dumps from 6.5 can be read but to me, it sounds better to
>have 2 boxes (or one box with two SQL instances). One with SQl 2000 and one
>with 6.5. Run the import database tool, which will copy all objects and data
>to SQL 2000.
>
Actually I want to resotre another 6.5 with a dump from the original.
Of course I can't even get the new one to work with the backup
database. I made sure its on the same hard drive letter and even
copied over the whole MSSQL folder but so far no luck.

6.5 to 6.5

I want to upgrade our 6.5 sql server to sql server 2000 but first I
want to create another 6.5 first. This way when I screw the pooch I
won't take down our only database.
Anyway I was planning on creating a new database and then restore it
with a dump from the original. If there is an easier way please let
me know.
I've been making daily backups via a CD burner of the folder MSSQL and
backing it up once a week with a dat drive. I"ve also started doing
the dumps each day also.
As you can probably tell I've very new to this.
We use the Platypus 3.0 database frontend by Boardtown.
Thanks for all the help you can give me.<kg7poe@.sti.net> wrote in message
news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.
4ax.com...
> I want to upgrade our 6.5 sql server to sql server 2000 but first I
> want to create another 6.5 first. This way when I screw the pooch I
> won't take down our only database.
> Anyway I was planning on creating a new database and then restore it
> with a dump from the original. If there is an easier way please let
> me know.
Not sure whether dumps from 6.5 can be read but to me, it sounds better to
have 2 boxes (or one box with two SQL instances). One with SQl 2000 and one
with 6.5. Run the import database tool, which will copy all objects and data
to SQL 2000.|||Hi,
(You cant restore a SQL 6.5 server database to SQL 2000 server due to
architectural changes.)
The only way to upgrade SQL 6.5 database to SQL 2000 is using the "Upgrade
Wizard" coming with SQL 2000.
You can either perform the upgrade :-
1. In the network using Named pipes protocol
2. Install SQL 6.5 in new server and have the upgrade in the same server
Steps for 1.
1. Install SQL 2000 and SP3a
2. Install SQL 6.5 sp5a
3. In the SQL 2000 server use the upgrade wizard to upgrade. This wizard
will point to a step by upgrade.
Steps for 2.
1. Install SQL 2000 and SP3a in New server
2. Install SQL 6.5 and SP5a ina new server (With the same folder structure
as existing server)
3. Stop SQL 6.5 server in both servers
4. Copy the physical DAT files (Data and log files) from Existing to new
server in the same folder including system databases
5. STArt SQL 6.5 in server, this will make the new SQL 6.5 server same as
existing
7. In the SQL 2000 server use the upgrade wizard to upgrade. This wizard
will point to a step by upgrade.
Second step will be fast since the upgrade is happening in the same machine.
Incase if you are using the First step then ensure that network is up and
stable.
Thanks
Hari
MCDBA
<kg7poe@.sti.net> wrote in message
news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.
4ax.com...
> I want to upgrade our 6.5 sql server to sql server 2000 but first I
> want to create another 6.5 first. This way when I screw the pooch I
> won't take down our only database.
> Anyway I was planning on creating a new database and then restore it
> with a dump from the original. If there is an easier way please let
> me know.
>
> I've been making daily backups via a CD burner of the folder MSSQL and
> backing it up once a week with a dat drive. I"ve also started doing
> the dumps each day also.
> As you can probably tell I've very new to this.
> We use the Platypus 3.0 database frontend by Boardtown.
>
> Thanks for all the help you can give me.|||On Sun, 16 May 2004 23:05:51 +0200, "Egbert Nierop \(MVP for IIS\)"
<egbert_nierop@.nospam.invalid> wrote:

><kg7poe@.sti.net> wrote in message
> news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.
4ax.com...
>Not sure whether dumps from 6.5 can be read but to me, it sounds better to
>have 2 boxes (or one box with two SQL instances). One with SQl 2000 and one
>with 6.5. Run the import database tool, which will copy all objects and dat
a
>to SQL 2000.
>
Actually I want to resotre another 6.5 with a dump from the original.
Of course I can't even get the new one to work with the backup
database. I made sure its on the same hard drive letter and even
copied over the whole MSSQL folder but so far no luck.

501 when connect to Endpoint

I Created SP and endpoint that exposes SP as web service :

CREATE PROCEDURE TimeServer.ResponseTime2
(
@.TimeType int,
)
AS
IF (@.TimeType = 0 )
SELECT @.Result AS CZAS
ELSE
SELECT @.Result AS CZAS
GO
CREATE ENDPOINT MyWebService
STATE = STARTED
AS HTTP
(
PATH = '/AdventureWorks/MyWebService',
AUTHENTICATION = (INTEGRATED ),
PORTS = ( CLEAR ),
SITE = 'localhost'
)
FOR SOAP
(
WEBMETHOD 'GetTime' (Name = 'AdventureWorks.TimeServer.ResponseTime2', FORMAT = ROWSETS_ONLY),
DATABASE = 'AdventureWorks'
)

GO

When I try to connect to webservice (localhost/AdventureWorks/MyWebServic
I get 501 error - Not implemented or not supported.

Any ideas why ?

I don't know if this answers your question. However, we support HTTP GET requests ONLY for requesting WSDL. In this case if you submitted the following request

http://localhost/AdventureWorks/MyWebService?wsdl

it should return WSDL describing the endpoint.

The rest of the SOAP requests have to be submitted via HTTP POST.

Thanks
Srik

|||

I was also getting this at one point. Try going into IE browser->Tools->Internet Options->Advanced and enable "Use HTTP 1.1 through proxy connections" if this is not set (may be related to proxy settings associated wih IE Browser->Connections->LAN Settings)

501 when connect to Endpoint

I Created SP and endpoint that exposes SP as web service :

CREATE PROCEDURE TimeServer.ResponseTime2
(
@.TimeType int,
)
AS
IF (@.TimeType = 0 )
SELECT @.Result AS CZAS
ELSE
SELECT @.Result AS CZAS
GO
CREATE ENDPOINT MyWebService
STATE = STARTED
AS HTTP
(
PATH = '/AdventureWorks/MyWebService',
AUTHENTICATION = (INTEGRATED ),
PORTS = ( CLEAR ),
SITE = 'localhost'
)
FOR SOAP
(
WEBMETHOD 'GetTime' (Name = 'AdventureWorks.TimeServer.ResponseTime2', FORMAT = ROWSETS_ONLY),
DATABASE = 'AdventureWorks'
)

GO

When I try to connect to webservice (localhost/AdventureWorks/MyWebServic
I get 501 error - Not implemented or not supported.

Any ideas why ?

I don't know if this answers your question. However, we support HTTP GET requests ONLY for requesting WSDL. In this case if you submitted the following request

http://localhost/AdventureWorks/MyWebService?wsdl

it should return WSDL describing the endpoint.

The rest of the SOAP requests have to be submitted via HTTP POST.

Thanks
Srik

|||

I was also getting this at one point. Try going into IE browser->Tools->Internet Options->Advanced and enable "Use HTTP 1.1 through proxy connections" if this is not set (may be related to proxy settings associated wih IE Browser->Connections->LAN Settings)