Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 89ded2b

Browse files
initial commit
1 parent ac6caf6 commit 89ded2b

28 files changed

+1834
-1
lines changed

‎ACKNOWLEDGMENTS.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
## Copyright notice:
2+
3+
LICENSE
4+
5+
Redistribution and use in source and binary forms, with or without
6+
modification, are permitted provided that the following conditions are met:
7+
8+
1. Redistributions of source code must retain the above copyright notice, this
9+
list of conditions and the following disclaimer.
10+
11+
2. Redistributions in binary form must reproduce the above copyright notice,
12+
this list of conditions and the following disclaimer in the documentation
13+
and/or other materials provided with the distribution.
14+
15+
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
16+
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
17+
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
18+
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
19+
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
20+
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
21+
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
22+
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
23+
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
24+
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
25+
26+
CONTRIBUTION AGREEMENT
27+
28+
By contributing to the repository through pull-request, comment, or otherwise, the contributor releases their content to the license and copyright terms herein.
29+

‎AUTHORS.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
### Note:
2+
###### This is the official list of authors for copyright purposes. This file is distinct from the CONTRIBUTORS files, see the latter for an explanation.
3+
###### Names should be added to this file as:
4+
Name or Organization <email@address> [website](http://domain.com)
5+
###### The email address is not required for organizations.
6+
7+
# Authors
8+
9+
Javier Cañon <javier@javiercanon.com> [website](https://www.javiercanon.com)

‎CHANGELOG.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Changelog
2+
3+
## [Unreleased]
4+
5+
6+
## 0.0.1 - 2020-XX-XX
7+
8+
### Added
9+
- This CHANGELOG file to hopefully serve as an evolving example of a
10+
standardized open source project CHANGELOG.
11+
12+
### Changed
13+
- Refer to a "change log" instead of a "CHANGELOG" throughout the site
14+
to differentiate between the file and the purpose of the file — the
15+
logging of changes.
16+
17+
### Removed
18+
- Remove empty sections from CHANGELOG, they occupy too much space and
19+
create too much noise in the file. People will have to assume that the
20+
missing sections were intentionally left out because they contained no
21+
notable changes.
22+
23+
24+
25+
###### Notes
26+
The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
27+
and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).

‎CODE_OF_CONDUCT.md

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
# Code of Conduct
2+
```Last Updated: 2018年01月01日 by [Javier Cañon](https://www.javiercanon.com)```
3+
4+
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
5+
6+
7+
## Our Standards
8+
9+
Examples of behavior that contributes to creating a positive environment include:
10+
11+
* Using welcoming and inclusive language
12+
* Being respectful of differing viewpoints and experiences
13+
* Gracefully accepting constructive criticism
14+
* Focusing on what is best for the community
15+
* Showing empathy towards other community members
16+
17+
Examples of unacceptable behavior by participants include:
18+
19+
* The use of sexualized language or imagery and unwelcome sexual attention or advances
20+
* Trolling, insulting/derogatory comments, and personal or political attacks
21+
* Public or private harassment
22+
* Publishing others' private information, such as a physical or electronic address, without explicit permission
23+
* Conduct which could reasonably be considered inappropriate for the forum in which it occurs.
24+
25+
All TensorFlow forums and spaces are meant for professional interactions, and any behavior which could reasonably be considered inappropriate in a professional setting is unacceptable.
26+
27+
28+
## Our Responsibilities
29+
30+
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
31+
32+
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
33+
34+
35+
## Scope
36+
37+
This Code of Conduct applies to all content on tensorflow.org, TensorFlow’s GitHub organization, or any other official TensorFlow web presence allowing for community interactions, as well as at all official TensorFlow events, whether offline or online.
38+
39+
The Code of Conduct also applies within project spaces and in public spaces whenever an individual is representing TensorFlow or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed or de facto representative at an online or offline event.
40+
41+
42+
## Conflict Resolution
43+
44+
Conflicts in an open source project can take many forms, from someone having a bad day and using harsh and hurtful language in the issue queue, to more serious instances such as sexist/racist statements or threats of violence, and everything in between.
45+
46+
If the behavior is threatening or harassing, or for other reasons requires immediate escalation, please see below.
47+
48+
However, for the vast majority of issues, we aim to empower individuals to first resolve conflicts themselves, asking for help when needed, and only after that fails to escalate further. This approach gives people more control over the outcome of their dispute.
49+
50+
If you are experiencing or witnessing conflict, we ask you to use the following escalation strategy to address the conflict:
51+
52+
1. Address the perceived conflict directly with those involved, preferably in a real-time medium.
53+
2. If this fails, get a third party (e.g. a mutual friend, and/or someone with background on the issue, but not involved in conflict) to intercede.
54+
3. If you are still unable to resolve the conflict, and you believe it rises to harassment or another code of conduct violation, report it.
55+
56+
57+
## Reporting Violations
58+
59+
Violations of the Code of Conduct can be reported to the Project owner, JAVIER CAÑON: [javier@javiercanon.com](mailto:javier@javiercanon.com) [www.javiercanon.com](https://www.javiercanon.com) . The Project Steward will determine whether the Code of Conduct was violated, and will issue an appropriate sanction, possibly including a written warning or expulsion from the project, project sponsored spaces, or project forums. We ask that you make a good-faith effort to resolve your conflict via the conflict resolution policy before submitting a report.
60+
61+
Violations of the Code of Conduct can occur in any setting, even those unrelated to the project. We will only consider complaints about conduct that has occurred within one year of the report.
62+
63+
64+
## Enforcement
65+
66+
If the Project Stewards receive a report alleging a violation of the Code of Conduct, the Project Stewards will notify the accused of the report, and provide them an opportunity to discuss the report before a sanction is issued. The Project Stewards will do their utmost to keep the reporter anonymous. If the act is ongoing (such as someone engaging in harassment), or involves a threat to anyone's safety (e.g. threats of violence), the Project Stewards may issue sanctions without notice.
67+
68+
69+
## Attribution
70+
71+
This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://contributor-covenant.org/version/1/4, and includes some aspects of the Geek Feminism Code of Conduct and the Drupal Code of Conduct.

‎CONTRIBUTING.md

Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
# Contributing guidelines
2+
```Last Updated: 2018年08月16日 by Javier Cañon```
3+
4+
## Pull Request Checklist
5+
6+
Before sending your pull requests, make sure you followed this list.
7+
8+
- Read [contributing guidelines](CONTRIBUTING.md).
9+
- Read [Code of Conduct](CODE_OF_CONDUCT.md).
10+
- Check if my changes are consistent with the guidelines.
11+
- Changes are consistent with the Coding Style.
12+
- Run Unit Tests.
13+
14+
## How to become a contributor and submit your own code
15+
16+
### Contributor License Agreements
17+
18+
We'd love to accept your patches! Before we can take them, we have to jump a couple of legal hurdles.
19+
Please read the License Agreement.
20+
***NOTE***: Only original source code from you and other people can be accepted into the main repository.
21+
22+
### Contributing code
23+
24+
If you have improvements to TensorFlow, send us your pull requests! For those
25+
just getting started, Github has a [howto](https://help.github.com/articles/using-pull-requests/).
26+
27+
TensorFlow team members will be assigned to review your pull requests. Once the pull requests are approved and pass continuous integration checks, we will merge the pull requests.
28+
For some pull requests, we will apply the patch for each pull request to our internal version control system first, and export the change out as a new commit later, at which point the original pull request will be closed. The commits in the pull request will be squashed into a single commit with the pull request creator as the author. These pull requests will be labeled as pending merge internally.
29+
30+
If you want to contribute but you're not sure where to start,
31+
take a look at the issues section.
32+
33+
These are issues that we believe are particularly well suited for outside
34+
contributions, often because we probably won't get to them right now. If you
35+
decide to start on an issue, leave a comment so that other people know that
36+
you're working on it. If you want to help out, but not alone, use the issue
37+
comment thread to coordinate.
38+
39+
### Contribution guidelines and standards
40+
41+
Before sending your pull request for review
42+
make sure your changes are consistent with the guidelines and follow the coding style.
43+
44+
#### General guidelines and philosophy for contribution
45+
46+
* Include unit tests when you contribute new features, as they help to
47+
a) prove that your code works correctly, and b) guard against future breaking
48+
changes to lower the maintenance cost.
49+
* Bug fixes also generally require unit tests, because the presence of bugs
50+
usually indicates insufficient test coverage.
51+
* Keep compatibility in mind when you change code in core;
52+
e.g., code has reached version 1 and hence cannot make
53+
non-backward-compatible changes without a major release. Reviewers of your
54+
pull request will comment on any compatibility issues.
55+
* When you contribute a new feature, the maintenance burden is (by
56+
default) transferred to the team. This means that benefit of the
57+
contribution must be compared against the cost of maintaining the feature.
58+
* Full new features (e.g., a new op implementing a cutting-edge algorithm)
59+
typically will live in a branch,to get some airtime before decision
60+
is made regarding whether they are to be migrated to the core.
61+
62+
#### License
63+
64+
Include a (the) license at the top of new files you can use a developer tool,
65+
e.g.: [License Header Manager](https://github.com/rubicon-oss/LicenseHeaderManager)
66+
67+
#### Coding style languages
68+
69+
* [Microsoft C# and .NET Style Guide](https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/)
70+
* [Google Java Style Guide](https://google.github.io/styleguide/javaguide.html)
71+
* [Google JavaScript Style Guide](https://google.github.io/styleguide/jsguide.html)
72+
* [Google Shell Style Guide](https://google.github.io/styleguide/shell.xml)
73+
* [Google Objective-C Style Guide](https://google.github.io/styleguide/objcguide.html)
74+
* [Google Python Style Guide](https://github.com/google/styleguide/blob/gh-pages/pyguide.md)
75+
* [Google C++ Style Guide](https://google.github.io/styleguide/cppguide.html).
76+
77+
78+
#### Running unit tests
79+
80+
There are many ways to run unit tests, like:
81+
1. Using tools and libraries installed directly on your system.
82+
2. Using [Docker](https://www.docker.com). [Microsoft Docker Help](https://docs.microsoft.com/en-us/dotnet/core/docker/).
83+
3. [Visual Studio Unit Testing](https://docs.microsoft.com/en-us/dotnet/core/testing/)
84+
85+

‎LICENSE renamed to ‎LICENSE.md

File renamed without changes.

‎Microsoft-SQL-Server-Scripts-Utils.sln

Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
2+
Microsoft Visual Studio Solution File, Format Version 12.00
3+
# Visual Studio Version 16
4+
VisualStudioVersion = 16.0.29920.165
5+
MinimumVisualStudioVersion = 10.0.40219.1
6+
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Solution Items", "Solution Items", "{F3D249A4-350F-4AAB-8C59-7BBD0AE2F2DE}"
7+
ProjectSection(SolutionItems) = preProject
8+
.gitignore = .gitignore
9+
ACKNOWLEDGMENTS.md = ACKNOWLEDGMENTS.md
10+
AUTHORS.md = AUTHORS.md
11+
CHANGELOG.md = CHANGELOG.md
12+
CODE_OF_CONDUCT.md = CODE_OF_CONDUCT.md
13+
CONTRIBUTING.md = CONTRIBUTING.md
14+
LICENSE.md = LICENSE.md
15+
README.md = README.md
16+
RELEASE.md = RELEASE.md
17+
Roadmap.md = Roadmap.md
18+
EndProjectSection
19+
EndProject
20+
Project("{E24C65DC-7377-472B-9ABA-BC803B73C61A}") = "src", "src\", "{6CDB34D4-18FB-4F97-983C-0CF00D644F85}"
21+
ProjectSection(WebsiteProperties) = preProject
22+
TargetFrameworkMoniker = ".NETFramework,Version%3Dv4.0"
23+
Debug.AspNetCompiler.VirtualPath = "/localhost_34131"
24+
Debug.AspNetCompiler.PhysicalPath = "src\"
25+
Debug.AspNetCompiler.TargetPath = "PrecompiledWeb\localhost_34131\"
26+
Debug.AspNetCompiler.Updateable = "true"
27+
Debug.AspNetCompiler.ForceOverwrite = "true"
28+
Debug.AspNetCompiler.FixedNames = "false"
29+
Debug.AspNetCompiler.Debug = "True"
30+
Release.AspNetCompiler.VirtualPath = "/localhost_34131"
31+
Release.AspNetCompiler.PhysicalPath = "src\"
32+
Release.AspNetCompiler.TargetPath = "PrecompiledWeb\localhost_34131\"
33+
Release.AspNetCompiler.Updateable = "true"
34+
Release.AspNetCompiler.ForceOverwrite = "true"
35+
Release.AspNetCompiler.FixedNames = "false"
36+
Release.AspNetCompiler.Debug = "False"
37+
VWDPort = "34131"
38+
SlnRelativePath = "src\"
39+
EndProjectSection
40+
EndProject
41+
Project("{E24C65DC-7377-472B-9ABA-BC803B73C61A}") = "docs", "docs\", "{171687C4-6EA6-413F-94F7-4A499A5827D9}"
42+
ProjectSection(WebsiteProperties) = preProject
43+
TargetFrameworkMoniker = ".NETFramework,Version%3Dv4.0"
44+
Debug.AspNetCompiler.VirtualPath = "/localhost_34134"
45+
Debug.AspNetCompiler.PhysicalPath = "docs\"
46+
Debug.AspNetCompiler.TargetPath = "PrecompiledWeb\localhost_34134\"
47+
Debug.AspNetCompiler.Updateable = "true"
48+
Debug.AspNetCompiler.ForceOverwrite = "true"
49+
Debug.AspNetCompiler.FixedNames = "false"
50+
Debug.AspNetCompiler.Debug = "True"
51+
Release.AspNetCompiler.VirtualPath = "/localhost_34134"
52+
Release.AspNetCompiler.PhysicalPath = "docs\"
53+
Release.AspNetCompiler.TargetPath = "PrecompiledWeb\localhost_34134\"
54+
Release.AspNetCompiler.Updateable = "true"
55+
Release.AspNetCompiler.ForceOverwrite = "true"
56+
Release.AspNetCompiler.FixedNames = "false"
57+
Release.AspNetCompiler.Debug = "False"
58+
VWDPort = "34134"
59+
SlnRelativePath = "docs\"
60+
EndProjectSection
61+
EndProject
62+
Global
63+
GlobalSection(SolutionConfigurationPlatforms) = preSolution
64+
Debug|Any CPU = Debug|Any CPU
65+
EndGlobalSection
66+
GlobalSection(ProjectConfigurationPlatforms) = postSolution
67+
{6CDB34D4-18FB-4F97-983C-0CF00D644F85}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
68+
{6CDB34D4-18FB-4F97-983C-0CF00D644F85}.Debug|Any CPU.Build.0 = Debug|Any CPU
69+
{171687C4-6EA6-413F-94F7-4A499A5827D9}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
70+
{171687C4-6EA6-413F-94F7-4A499A5827D9}.Debug|Any CPU.Build.0 = Debug|Any CPU
71+
EndGlobalSection
72+
GlobalSection(SolutionProperties) = preSolution
73+
HideSolutionNode = FALSE
74+
EndGlobalSection
75+
GlobalSection(ExtensibilityGlobals) = postSolution
76+
SolutionGuid = {FFCF5984-25C1-4C3E-8CDE-26F6AB8CB465}
77+
EndGlobalSection
78+
EndGlobal
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
extensions: designer.cs generated.cs
2+
extensions: .cs .cpp .h
3+
// MIT LICENSE Copyright (c) 2020 Javier Cañon | www.javiercanon.com
4+
extensions: .sql
5+
/* MIT LICENSE Copyright (c) 2020 Javier Cañon | www.javiercanon.com */
6+
extensions: .aspx .ascx
7+
<%--
8+
MIT LICENSE Copyright (c) 2020 Javier Cañon | www.javiercanon.com
9+
--%>
10+
extensions: .vb
11+
'MIT LICENSE Copyright (c) 2020 Javier Cañon | www.javiercanon.com
12+
extensions: .xml .config .xsd
13+
<!--
14+
MIT LICENSE Copyright (c) 2020 Javier Cañon | www.javiercanon.com
15+
-->

‎README.md

Lines changed: 55 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,56 @@
11
# Microsoft-SQL-Server-Scripts-Utils
2-
Utility scripts for Microsoft Sql Server
2+
3+
Utility scripts, functions and stored procedures for Microsoft Sql Server.
4+
5+
The name of the folder contains de script with the minimoun version for compatibility for that script.
6+
7+
## Philosophy of Javier Cañon
8+
* KISS by design and programming. An acronym for "keep it simple, stupid" or "keep it stupid simple", is a design principle. The KISS principle states that most systems work best if they are kept simple rather than made complicated; therefore, simplicity should be a key goal in design, and unnecessary complexity should be avoided. Variations on the phrase include: "Keep it simple, silly", "keep it short and simple", "keep it simple and straightforward", "keep it small and simple", or "keep it stupid simple".
9+
10+
* Select the best tools for the job, use tools that take less time to finish the job.
11+
* Productivity over complexity and avoid unnecessary complexity for elegant or beauty code.
12+
13+
* Computers are machines, more powerful every year, give them hard work, concentrate on being productive.
14+
15+
16+
## Issues and Bug Traking ##
17+
Please submit *bug reports* or *feature requests* on GitHub:
18+
* [Issue | Request Features](https://github.com/JavierCanon/Microsoft-SQL-Server-Scripts-Utils/issues)
19+
20+
## Requeriments ##
21+
22+
* Microsoft SQL Server, Any Edition
23+
24+
25+
## Contributing
26+
27+
Please read [CONTRIBUTING.md](/CONTRIBUTING.md) for details on our code of conduct, and the process for submitting pull requests to us.
28+
29+
30+
## Versioning
31+
32+
We use [SemVer](http://semver.org/) for versioning. For the versions available, see the [tags on this repository](https://github.com/your/project/tags).
33+
34+
## Authors
35+
36+
* **Javier Cañon** - *Initial work* - [www.JavierCanon.com](https://www.javiercanon.com)
37+
38+
See also the list of [contributors](/AUTHORS.md) who participated in this project.
39+
40+
41+
## Supported by, thanks to
42+
43+
![Softcanon](https://github.com/JavierCanon/Social-Office-Webackeitor/raw/master/docs/images/logo_softcanon_200x75.gif)
44+
45+
[Softcanon](https://www.softcanon.com)
46+
--
47+
48+
* [SQL Pretty Printer for SQL Server](http://www.dpriver.com/products/sqlpp/index.php)
49+
--
50+
51+
## License
52+
53+
This project is licensed under the MIT LICENSE - see the [LICENSE.md](/LICENSE.md) file for details.
54+
55+
---
56+
Made with ❤️ by **[Javier Cañon](https://www.javiercanon.com)**.

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /