Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SQL Server Hosting - Support Jobs
- Thread starter vbkris
- Start date
NoCoolHandle
Programmer
You might try webhost4life.com
They definitly support asp and asp.net vr 1 and 1.1
They have sql, but I suspect you will need to create your own jobs via storedprocs..
I can't remember seeing jobs as part of their web version of EM. but I wasn't looking for it either.
They are Cheep and seem to run a pretty good ship.
Basic hosting (aspx and sqlserver 300mb + 300mb diskspace = $10 per month!)
Anytime I have sent them a reqest for information they have been very fast and any issues our site has experienced seems to get resolved within the hour (of me finding out and posting them a Q about why)
HTH
Rob
They definitly support asp and asp.net vr 1 and 1.1
They have sql, but I suspect you will need to create your own jobs via storedprocs..
I can't remember seeing jobs as part of their web version of EM. but I wasn't looking for it either.
They are Cheep and seem to run a pretty good ship.
Basic hosting (aspx and sqlserver 300mb + 300mb diskspace = $10 per month!)
Anytime I have sent them a reqest for information they have been very fast and any issues our site has experienced seems to get resolved within the hour (of me finding out and posting them a Q about why)
HTH
Rob
- Thread starter
- #3
NoCoolHandle
Programmer
Another thought, go to the Microsoft.com aspnet site. I remember them listing a number of websites that host aspnet. (I think I might have found webhost4life there..)
Everyone seems to offer different features.
Post back with your finds as this might be usefull in the future.
For bulk jobs and maintence tasks I have been building webservices and executing them from a system back here. Then I can schedule the task and usually do what I would need. Kind of a workaround but it does work and building webservices couldn;t be easier with Dotnet.
Rob
Everyone seems to offer different features.
Post back with your finds as this might be usefull in the future.
For bulk jobs and maintence tasks I have been building webservices and executing them from a system back here. Then I can schedule the task and usually do what I would need. Kind of a workaround but it does work and building webservices couldn;t be easier with Dotnet.
Rob
- Thread starter
- #5
NoCoolHandle
Programmer
Yeah the cool thing about webservices is that you can literally do anything with them.
I build a site for a friend who is a photograper. it is dymanic and allows him to just upload images and it builds the pages for them. All the images are stored in the db. Using traditional asp or html file uploads were 1 file at a time.
I played with building a webservce and now he can maintain his entire image db from his home or through a firewall (as it is http) He can upload an entire directory of files in 1 action. It is also usefull for updating category information and doing just about anything on the DB.
But the bottom line is webservices can do anything you can do in code and be executed easily via a small vb app or a webpage and all you need to be able to do is schedule the action on a pc connected to the inet.
If you want some sample code post back
Rob
I build a site for a friend who is a photograper. it is dymanic and allows him to just upload images and it builds the pages for them. All the images are stored in the db. Using traditional asp or html file uploads were 1 file at a time.
I played with building a webservce and now he can maintain his entire image db from his home or through a firewall (as it is http) He can upload an entire directory of files in 1 action. It is also usefull for updating category information and doing just about anything on the DB.
But the bottom line is webservices can do anything you can do in code and be executed easily via a small vb app or a webpage and all you need to be able to do is schedule the action on a pc connected to the inet.
If you want some sample code post back
Rob
- Thread starter
- #7
NoCoolHandle
Programmer
yes re the asmx file
I have then running on the webserver (webhost4life) and execute them via a local (on my pc or my friends pc) vb.net application.
But because an asmx file (webservice) can take arguments like a vb class (which is what they are) you can submit an entire datatable (filled to the gills with blobs) to your webserver in a single action.
Kind of like superman. They can leap tall buildings in a single bound.
But they definitly open up possibilities for remote control and maintenence of your website and database.
VERY VERY COOL!
Rob
I have then running on the webserver (webhost4life) and execute them via a local (on my pc or my friends pc) vb.net application.
But because an asmx file (webservice) can take arguments like a vb class (which is what they are) you can submit an entire datatable (filled to the gills with blobs) to your webserver in a single action.
Kind of like superman. They can leap tall buildings in a single bound.
But they definitly open up possibilities for remote control and maintenence of your website and database.
VERY VERY COOL!
Rob
- Thread starter
- #9
- Thread starter
- #10
i dont know if this is the right forum but here goes:
isnt a webserverice open to ANY user? so not only can ur firend use it, any one who stumbles upon it can use it (thanks to the inbuilt help for the web service)...
Known is handfull, Unknown is worldfull
isnt a webserverice open to ANY user? so not only can ur firend use it, any one who stumbles upon it can use it (thanks to the inbuilt help for the web service)...
Known is handfull, Unknown is worldfull
NoCoolHandle
Programmer
Yes and no..
To get at it's wsdl you need to know it is there.
Then when you get into the .aspx site, you can use forms authentication or build your own authentication methods directly into the webservice.
But the bottom line is that a web server isn't going to advertise it's presence (without your explicit permissions and a couple of extra steps).. Bury it a couple of directorys and it would be hard for anyone to find it if they don't know it is there. (make sure you have no links to it or a spider might find it)
Rob
To get at it's wsdl you need to know it is there.
Then when you get into the .aspx site, you can use forms authentication or build your own authentication methods directly into the webservice.
But the bottom line is that a web server isn't going to advertise it's presence (without your explicit permissions and a couple of extra steps).. Bury it a couple of directorys and it would be hard for anyone to find it if they don't know it is there. (make sure you have no links to it or a spider might find it)
Rob
- Thread starter
- #12
- Status
Similar threads
- Locked
- Question
- Locked
- Question
