Can no longer get dataset fill method to work after directory copy

I have been creating a small winforms app using VS 2005 and SQL Express. I
create serveral tables in the database and added it as the datasource for th
e
project. I created several forms, created several datagrids and regular
design views. After I got several of the forms running, I decided to backup
my directory and copied the entire directory to a backup directory on my har
d
drive.
While continuing to work on my project, the IDE lost some of the data
adapters and and datasets while I was switching between the design view and
code view. So I decided to delete the directory and copy the backup I had
saved and start from there. But a Big Problem occured. Once I opned the
project and tried to execute it, I could no longer get the app to connect to
the database. I am the only user and administrator account but every time th
e
app tries to fill a table now I get on of these two erors:
System.Data.SqlClient.SqlException was unhandled
Message="Unable to open the physical file -- ". Operating system error
5: \"5(Access is denied.)\".\r\nUnable to open the physical file
or
System.Data.SqlClient.SqlException was unhandled
Message="Cannot open user default database. Login failed.\r\nLogin failed
for user
Source=".Net SqlClient Data Provider"
ErrorCode=-2146232060
Class=11
LineNumber=65536
Number=4064
Procedure=""
Server=".\\SQLEXPRESS"
State=1
StackTrace:
I can no longer connect to the database even thou I can see and work with it
in the IDE. Help
HWDotNetDeveloperSeveral possible reasons for this:
1) you did not restore your original LDF file with your matching MDF
2) you have not re-attached the database
3) you are trying to connect using an sql user account and it is not config
ured the same with the "backed" up version
4) you are trying to connect without the correct user instance reference (i
e. the backed up version is different from the one you deleted)
If you can see the database from the IDE, then using query analyzer and run
a test query. You can also start OSQL and run a simple query against the da
tabase. If these queries work, then there is something not synchronized wit
hin your code versus the database that was restored.
Check out
http://msdn.microsoft.com/library/d...>
userinst.asp
Hope this helps...
-Eric

Can MS-SQL Access photo datatype data?

I am wondering if the MS-SQL can read or write files of photo-typed data.
What method or script I should notice if MS-SQL is no problem on accessing
photo-typed data.

Thanks any way!

Wilbertsorry, not following you there I'm afraid, can you clarify your question?

j|||Sorry for my poor English. I am from Taiwan.
Actually I have seen the artiles you posted on this Forums.
And thank you again for looking at my question.
Ok, I try my best to clarify my question.
I want to make a webpage which connects to a DB in order to for user upload or download image data from DB.
Primaryly I want to take advantage of DB to manage image data instead of a file folders created at purpose for storing image data.
That's all

Thank you, Atrax|||ah, I see. . I thought youmight mean this but wasn't sure.

my usualy advice is don't store image data (or other potentially large binaries) in SQL Server unless you have a very, very good reason. 99 times out of 100 it's better to store the image itself as a file, and then store the path to the file in the SQL Server. Storing a lot of image data can bloat your database rapidly, is more work to display (hence more strain on the server) and less easy to move around.

this isn't to say it can't be done - I've done it in the past - but it IS to say usually it's not such a grand idea. Have you got a good reason to do so?|||Actually that advice is out of date. It was still true to some extent for SS7 but MS did a lot of work to optimize SS2K for storing binary data. I think it was in response to other database engines that do it efficiently.

There should be an architectural reason to store binary data or to avoid it. But it just doesn't drain SQL Server like it used to.

Don|||storage isn't as bad as it used to be, but pulling data backwards and forwards, as you probably would - is less efficient. that's the major reason.|||Well,
First of all, I have to say in advanced that I am new to coding with vb.net even the
MS-SQL. For the security issue and efficiency in management of data ,
using folders or DB to stroe image data , which way is better? and Why?

Thank you all,

Wilbert|||That's hard to say. It really is an architectural decision that depends on the requirements of your app.

First, what is the security issue? Are you trying to protect the binary images or the other data in the database? Do you want to control access to the images? You can do that using Windows file system security. What is required for your application?

The answer to what is most efficient depends on how you're using the images. Are they in constant use, or might a particular image be accessed only once a year? How large are they? How many are there? Do you have to store a lot of information with them in the records?

Tell us more about your application and we'll try to give you more specifics.

Don|||Hi donkiely,

In my work place, one of my job now is to post the image to our website
and keep the imformation up to date. For this website just start, the data now is not huge.
These image are photoed from newspapers. We will find news related to my company on newspaper. If there are news which are suitable for posting to our website. I take it down.
We are setting these thing to record what thing happen in our company.
Sometime I will just take one picture a day and sometime I also could take more 10 pictures a day. Something I am sure that the quantity will go up quickly.
As the information above, Can it give you a picture or architectural thing that might
help my question.

With Regards

P.S. Please be patient of my poor English.

Wilbert|||Hi Wilbert,

That sounds like a reasonable use of images in the db, based on your description.

Here's an article that will give you the details.

Don|||Thank you, Donkiely

Can I use a Web Service Method as a Data Source

Can I use a Web Service Method as a Data Source in Report Creation.
Any help will be greatly appreciated.
Vishwanathan RamanYes you can definitely do that. It does involve a bit of work though. You'll
need to built a custom data extension (there's a sample on creating a data
extension for an ADO.NET dataset on MSDN) that will call the web service and
provide the report with the results of the call.
"Vishwanathan Raman" <VishwanathanRaman@.discussions.microsoft.com> wrote in
message news:C7DF2501-D37D-44B0-A1CE-F027741942B4@.microsoft.com...
> Can I use a Web Service Method as a Data Source in Report Creation.
> Any help will be greatly appreciated.
> Vishwanathan Raman
>

Can I restore msdb from another sqlserver 's backup

My msdb,system database, of sqlserver is marked suspected,
I cant recovery it for any method.
Therefore, Can I restore it from another sqlserver's
msdb backup?
Hi,
It is not required to restore the MSDB from another server. Best option
will be drop the MSDB database and run the INSTMSDB.SQL script
from sql server installation directory\install folder.
Follow the below steps:-
1. Login to sql server using query analyzer
2. Drop the MSD database
DROP database MSDB
3. Open the INSTMSDB.SQL file in query analyzer
4. Just execute the script. This create the MSDB database, ALL objects ,
......
5. After the succesful execution you will get a fresh MSDB.
Thanks
Hari
MCDBA
"StarNet" <anonymous@.discussions.microsoft.com> wrote in message
news:9e5b01c4792d$3cf98050$a601280a@.phx.gbl...
> My msdb,system database, of sqlserver is marked suspected,
> I cant recovery it for any method.
> Therefore, Can I restore it from another sqlserver's
> msdb backup?
|||Hi,
We have the same problem with a suspected MSDB.
We tried to drop the msdb but got the message that the database cannot be
droped because it'a a system database.
How can we drop the database anyway and solve our problem?
Best Regards,
Karin W
"Hari Prasad" wrote:

> Hi,
> It is not required to restore the MSDB from another server. Best option
> will be drop the MSDB database and run the INSTMSDB.SQL script
> from sql server installation directory\install folder.
> Follow the below steps:-
> 1. Login to sql server using query analyzer
> 2. Drop the MSD database
> DROP database MSDB
> 3. Open the INSTMSDB.SQL file in query analyzer
> 4. Just execute the script. This create the MSDB database, ALL objects ,
> ......
> 5. After the succesful execution you will get a fresh MSDB.
> Thanks
> Hari
> MCDBA
>
> "StarNet" <anonymous@.discussions.microsoft.com> wrote in message
> news:9e5b01c4792d$3cf98050$a601280a@.phx.gbl...
>
>
|||You should find info on this in KB 224071.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Karin W" <Karin W@.discussions.microsoft.com> wrote in message
news:417700A9-7115-481C-8884-BA26136A8E93@.microsoft.com...[vbcol=seagreen]
> Hi,
> We have the same problem with a suspected MSDB.
> We tried to drop the msdb but got the message that the database cannot be
> droped because it'a a system database.
> How can we drop the database anyway and solve our problem?
> Best Regards,
> Karin W
> "Hari Prasad" wrote:

Can I restore msdb from another sqlserver 's backup

My msdb,system database, of sqlserver is marked suspected,
I cant recovery it for any method.
Therefore, Can I restore it from another sqlserver's
msdb backup?Hi,
It is not required to restore the MSDB from another server. Best option
will be drop the MSDB database and run the INSTMSDB.SQL script
from sql server installation directory\install folder.
Follow the below steps:-
1. Login to sql server using query analyzer
2. Drop the MSD database
DROP database MSDB
3. Open the INSTMSDB.SQL file in query analyzer
4. Just execute the script. This create the MSDB database, ALL objects ,
.....
5. After the succesful execution you will get a fresh MSDB.
Thanks
Hari
MCDBA
"StarNet" <anonymous@.discussions.microsoft.com> wrote in message
news:9e5b01c4792d$3cf98050$a601280a@.phx.gbl...
> My msdb,system database, of sqlserver is marked suspected,
> I cant recovery it for any method.
> Therefore, Can I restore it from another sqlserver's
> msdb backup?|||Hi,
We have the same problem with a suspected MSDB.
We tried to drop the msdb but got the message that the database cannot be
droped because it'a a system database.
How can we drop the database anyway and solve our problem?
Best Regards,
Karin W
"Hari Prasad" wrote:
> Hi,
> It is not required to restore the MSDB from another server. Best option
> will be drop the MSDB database and run the INSTMSDB.SQL script
> from sql server installation directory\install folder.
> Follow the below steps:-
> 1. Login to sql server using query analyzer
> 2. Drop the MSD database
> DROP database MSDB
> 3. Open the INSTMSDB.SQL file in query analyzer
> 4. Just execute the script. This create the MSDB database, ALL objects ,
> ......
> 5. After the succesful execution you will get a fresh MSDB.
> Thanks
> Hari
> MCDBA
>
> "StarNet" <anonymous@.discussions.microsoft.com> wrote in message
> news:9e5b01c4792d$3cf98050$a601280a@.phx.gbl...
> > My msdb,system database, of sqlserver is marked suspected,
> > I cant recovery it for any method.
> > Therefore, Can I restore it from another sqlserver's
> > msdb backup?
>
>|||You should find info on this in KB 224071.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Karin W" <Karin W@.discussions.microsoft.com> wrote in message
news:417700A9-7115-481C-8884-BA26136A8E93@.microsoft.com...
> Hi,
> We have the same problem with a suspected MSDB.
> We tried to drop the msdb but got the message that the database cannot be
> droped because it'a a system database.
> How can we drop the database anyway and solve our problem?
> Best Regards,
> Karin W
> "Hari Prasad" wrote:
> > Hi,
> >
> > It is not required to restore the MSDB from another server. Best option
> > will be drop the MSDB database and run the INSTMSDB.SQL script
> > from sql server installation directory\install folder.
> >
> > Follow the below steps:-
> >
> > 1. Login to sql server using query analyzer
> > 2. Drop the MSD database
> >
> > DROP database MSDB
> >
> > 3. Open the INSTMSDB.SQL file in query analyzer
> >
> > 4. Just execute the script. This create the MSDB database, ALL objects ,
> > ......
> >
> > 5. After the succesful execution you will get a fresh MSDB.
> >
> > Thanks
> > Hari
> > MCDBA
> >
> >
> > "StarNet" <anonymous@.discussions.microsoft.com> wrote in message
> > news:9e5b01c4792d$3cf98050$a601280a@.phx.gbl...
> > > My msdb,system database, of sqlserver is marked suspected,
> > > I cant recovery it for any method.
> > > Therefore, Can I restore it from another sqlserver's
> > > msdb backup?
> >
> >
> >

Can I restore msdb from another sqlserver 's backup

My msdb,system database, of sqlserver is marked suspected,
I cant recovery it for any method.
Therefore, Can I restore it from another sqlserver's
msdb backup?Hi,
It is not required to restore the MSDB from another server. Best option
will be drop the MSDB database and run the INSTMSDB.SQL script
from sql server installation directory\install folder.
Follow the below steps:-
1. Login to sql server using query analyzer
2. Drop the MSD database
DROP database MSDB
3. Open the INSTMSDB.SQL file in query analyzer
4. Just execute the script. This create the MSDB database, ALL objects ,
.....
5. After the succesful execution you will get a fresh MSDB.
Thanks
Hari
MCDBA
"StarNet" <anonymous@.discussions.microsoft.com> wrote in message
news:9e5b01c4792d$3cf98050$a601280a@.phx.gbl...
> My msdb,system database, of sqlserver is marked suspected,
> I cant recovery it for any method.
> Therefore, Can I restore it from another sqlserver's
> msdb backup?|||Hi,
We have the same problem with a suspected MSDB.
We tried to drop the msdb but got the message that the database cannot be
droped because it'a a system database.
How can we drop the database anyway and solve our problem?
Best Regards,
Karin W
"Hari Prasad" wrote:

> Hi,
> It is not required to restore the MSDB from another server. Best option
> will be drop the MSDB database and run the INSTMSDB.SQL script
> from sql server installation directory\install folder.
> Follow the below steps:-
> 1. Login to sql server using query analyzer
> 2. Drop the MSD database
> DROP database MSDB
> 3. Open the INSTMSDB.SQL file in query analyzer
> 4. Just execute the script. This create the MSDB database, ALL objects ,
> ......
> 5. After the succesful execution you will get a fresh MSDB.
> Thanks
> Hari
> MCDBA
>
> "StarNet" <anonymous@.discussions.microsoft.com> wrote in message
> news:9e5b01c4792d$3cf98050$a601280a@.phx.gbl...
>
>|||You should find info on this in KB 224071.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Karin W" <Karin W@.discussions.microsoft.com> wrote in message
news:417700A9-7115-481C-8884-BA26136A8E93@.microsoft.com...[vbcol=seagreen]
> Hi,
> We have the same problem with a suspected MSDB.
> We tried to drop the msdb but got the message that the database cannot be
> droped because it'a a system database.
> How can we drop the database anyway and solve our problem?
> Best Regards,
> Karin W
> "Hari Prasad" wrote:
>

Can I pull the data to an existing table?

I am building RDA process between SQL server and SQL server CE. Since when we use the method 'SqlCeRemoteDataAccess.pull()', the data will be pulled down from SQL server to CE server and a new table is created with some addtional columns. As I only intend to pull the data and never push it back to SQL server, if I pull the data down for the second time, there will be an error saying that table is already existing. I wonder whether I can pull the data to an existing table everytime I do the RDA?
Thanks,
JustinRDA doesn't keep track of incremental changes from the server. If you want to update the client with new changes from the server, RDA requires that the table at the client be dropped and re-created via pull.

http://msdn2.microsoft.com/en-us/library/ms240401(en-US,SQL.90).aspx